Slack has made its Code API generally available, letting developers build agents that open dedicated code channels for substantial tasks. The change gives teams a place to follow an agent’s work, add context and review changes, rather than leaving the task in a private chat window.
Salesforce Watch analysis
What happened
A code channel is a dedicated Slack space an agent can create from a conversation when a request needs more than a quick reply. Developers can have their agents bring in relevant people and files, post progress and artefacts, and archive the channel when the work is done. Slack says the API is available on all Slack plans.
The API is designed to let agents show material such as code diffs, HTML previews and reasoning steps, while using Slack’s channel permissions and admin controls. Slack says message compliance is built in, and teammates can see what an agent is doing and who approved it. GitHub Copilot, one of the launch partners, opens a code channel in 30% of its agent sessions, according to Slack.
Why it matters
Coding agents often do their work out of sight, with context scattered between a person’s prompt, a separate tool and a code review. Slack’s API is an attempt to make that work collaborative: colleagues can redirect an agent mid-task, contribute knowledge and leave a record others can find later.
That could be useful for work that involves several steps or several people, such as debugging an incident or preparing a code change. It also gives developers a way to bring their own agents into Slack, rather than relying only on the handful of integrations already available. The 30% figure is Slack’s account of Copilot use, not an independent measure of how often code channels help.
Our read
The appealing idea is not that an agent can post in another app. It is that a team can see the work, add missing context and decide what happens next without building a whole collaboration interface from scratch. That is a more practical pitch than “AI, but with a channel”.
Slack also wants to be a neutral home for agents, so teams can change models or tools without moving the conversation. The test is whether this shared record makes agent work easier to guide and review, rather than simply giving everyone a front-row seat to a longer bot monologue.
What to watch
- Which agents and Slack plans support code channels in practice.
- Whether teams can clearly review proposed changes and approval history.
- How the API handles permissions and data boundaries in real deployments.
- Whether the forthcoming GitHub pull-request features make review and merge genuinely smoother.
Discussion spark: Would a shared Slack channel make you more willing to use coding agents at work, or does it risk turning a reviewable task into a busier one?
Sources and evidence
- Introducing the Slack Code API: Your agents, your team, one code channel (28 October 2026, 15:15 UTC)
not affiliated with or endorsed by Salesforce