Any developer can now build a Slack code channel for their own agent

Salesforce has made the Slack Code API generally available on all Slack plans, according to its announcement. Any developer can now build an agent that opens a code channel, adds people and files, posts updates and archives the channel when done.

What developers get with the API

Slack Code launched in August with partners including Anthropic, Cognition, GitHub and Vercel. Its central idea is the code channel: a dedicated space an agent opens for a task, with the relevant people, context and plan already inside. Teammates can watch the agent work, add context and approve changes without leaving Slack.

Salesforce says more than 150 customers and partners asked for access to build the same experience for their own agents, while only a handful of partners had it. The API removes that limit. It targets two groups: enterprises building in-house agents, and vendors publishing agents to the Slack Marketplace.

According to Salesforce, developers add the API to their agent manifest and set the properties of a code channel, such as its name, commands and views. When a teammate mentions the agent in a channel or DM and the request needs more than a quick reply, the agent creates the channel itself and adds bookmarks and artifacts. Slack supplies the interface for code diffs, HTML previews and thinking steps, so developers do not have to build their own review screens.

Governance is inherited. Salesforce says the agent takes on the permissions and admin controls of the channel it works in, message compliance is built in, and IT has no new access model to configure. Salesforce also says Slack stays neutral about which agent or model sits behind a channel, so teams can swap them later.

Salesforce cites GitHub Copilot as evidence the format works: it opens a dedicated code channel on 30% of its agent sessions. In the announcement, GitHub says the appeal is being able to “see what the agent has worked on and steer it right from inside Slack”.

Pull request tools and a new agents tab are still coming

Two pieces are labeled “available soon” and are not part of today’s release. The first is an upgraded pull request experience for teams using GitHub. Users will be able to request reviews from people inside Slack, and comments will sync both ways between Slack and GitHub. Once a PR is approved and tests pass, the code channel will offer a prompt to merge it.

The second is an enhanced Agents & Tools tab. It is meant to show code channels with their status, membership and recent context in one place, and to let people browse public code channels. Salesforce gives no dates for either feature.

The company lists Claude, Devin, GitHub Copilot and Vercel as agents already working with Slack Code in the Marketplace. The announcement names no pricing for the API and says nothing about rate limits or usage caps, only that it is available on all plans.

What to watch as the API leaves the partner circle

The change matters because of how restricted access was before. When Slack Code launched on August 20, The New Stack reported that code channel API access was limited to the launch partners, with a plan to open it to more coding agents later. Today’s release is that plan carried out, and it turns code channels from a feature of four vendors into a surface any agent can claim.

The first test is adoption outside the launch group. The Marketplace listing is the place to look: whether homegrown enterprise agents and new vendors appear there, or whether the same four names remain the only visible examples. Salesforce reports no count of agents built on the API so far, and the 150-plus requests it cites are interest, not shipped products.

The second is the contrast with other agent hooks into Slack. Anthropic’s Claude Tag, which lets people mention Claude in Slack channels, got an admin API in beta only weeks ago. As we reported, that API has 14 endpoints, is limited to Enterprise organizations and covers Slack only. The Slack Code API serves a different purpose, since it is for builders of agents rather than for admins configuring one vendor’s product. Even so, the difference in audience and plan restrictions shows how many agent surfaces Slack now hosts.

The third is the pull request flow. Salesforce says every high-stakes change can be approved by a person and that records remain searchable after archiving. Those claims are the company’s own, and the announcement includes no independent testing or customer data beyond the GitHub figure. Whether teams actually use channel approvals, or still merge directly in GitHub, will show up once the PR features ship.

For teams that already run agents elsewhere, the practical question is migration cost. Salesforce says developers can skip building diff viewers and review screens, but the announcement does not describe how an existing agent maps onto the manifest properties, or what happens to channels at large scale. The API documentation, which Salesforce points to, is where those details will be settled.