Salesforce put four coding agents inside Slack channels, free on every plan

Slack Code shipped August 20. You tag a coding agent in a conversation, it opens a project-specific channel, and the whole team watches the work happen: diffs, live HTML previews, feedback the agent picks up mid-run, approval gates before anything ships. Each channel keeps an audit log and archives itself when the assignment completes. Claude, ChatGPT, Devin, and Copilot are the founding partners. Hacker News

The free-on-every-plan part is the aggressive move. Salesforce isn't monetizing this directly, which means the product is the surface, not the feature. Every agent run that happens in Slack is a run that doesn't happen in Cursor's cloud, GitHub's Actions log, or somebody's terminal where nobody else can see it.

Four founding partners rather than an Agentforce-only play tells you Salesforce read the room correctly. Nobody wants agent orchestration locked to the vendor whose CRM they're already annoyed about. A neutral surface with four harnesses on it is a genuinely different pitch than "our agent, in our chat."

The HN thread ran 75 points and 102 comments, which is a comment-heavy, upvote-light shape. That ratio almost always means argument rather than enthusiasm, and the argument is worth having. Putting agent runs in a chat channel makes them visible, which is good, and makes them conversational, which is a mixed blessing. Code review in Slack has been tried by every team that ever wanted to avoid GitHub, and it fails in the same way each time: the channel scrolls, the context evaporates, and the decision that mattered is three days up the history with no permalink anyone remembers. Self-archiving channels partially address this, but archiving is not the same as durable, searchable, linked-from-the-commit review.

Where I think this genuinely lands is the handoff problem. If your team is already scripting agent kickoffs through a Slack bot (and a lot are, including the Cursor team's own workflow, which we'll get to), you've built an ad-hoc version of this with worse permissions and no audit log. Slack Code replaces that duct tape with something maintained by the vendor whose auth you already trust. Take it for the audit trail and the approval gate, and keep your actual code review where it has line anchors.

One more thread to pull: Salesforce shipped a Headless 360 MCP Server the day before, and took the Slackbot MCP Client to GA connecting to 20-plus partner apps including Atlassian, Box, Linear, and Notion, with identity resolving per user rather than through a shared service account (Salesforce). Slack Code isn't a standalone launch. It's the visible half of Salesforce trying to become the place agents get invoked and the place their permissions get resolved.