Slack Code opens dedicated channels for teams and coding agents

Slack has shipped Slack Code. Mention a coding agent on a real task, and Slack says a dedicated code channel spins up around that job — visible to the team, built for diffs and previews instead of a cramped thread, then archived when the work is done.

That is the product, not a rumor. Agent coding has mostly been a private-tab workflow. Slack is trying to make it multiplayer and auditable in the chat tool most teams already use, with a short list of partners live on day one. The Register covered the launch on 20 August 2026.

Tag an agent, get a room for one task

You mention a coding agent on a complex project. A code channel appears, scoped to that work, and can pull in anyone on the team. The agent shapes the space around what the task needs: a code diff, a planning doc, or a live HTML preview, rather than pasting a wall of text into a thread.

When the job finishes, the channel archives itself. Slack describes the leftover as an audit log that stays searchable. The Register's recap matches: each channel maps to a particular project, so the main company chat is not flooded with an agent narrating a rewrite.

Slack says it built this because multi-turn agent work felt cramped in a standard thread, while a private browser tab hid the work from everyone else. Internally, it claims over 70% of code channels spin up and close within a single day, from idea to merged pull request.

Diffs, previews, and a human on the merge

The room is meant to show more than chat. Slack and Salesforce both say teammates can follow the conversation, review code diffs, and check live previews in place. Anyone in the channel can pause, redirect, or stop the agent if it drifts.

High-stakes moves are supposed to stay human-gated. Slack says those changes can route to a person for a fast in-channel approval. Salesforce is more specific: for actions such as pushing code to production, the agent packages the work for an expert to sign off in the same room.

The pitch is not only for engineers. Slack's running example — also reported by The Register — has a product manager spotting a bug, asking an agent to propose a fix, then tagging an engineer to check the diff and preview before the agent opens a pull request. Slack's line on that flow: "No ticket, no meeting, no waiting — just a fix, shipped."

Agents inherit Slack's existing permissions, security policies, and admin controls. Salesforce says there is no extra IT lift and no new identities to manage. GitHub's Copilot-in-Slack docs add a partner-side warning: Copilot may create pull requests or issues using the linked GitHub account's permissions, and it can capture an entire Slack thread as context unless you keep the prompt in a tighter DM.

Who is live, and who is "soon"

Slack's availability section is the one to trust for shipping status. Slack Code is live today for teams using:

Claude from Anthropic
Devin from Cognition
GitHub Copilot
Vercel

OpenAI's ChatGPT is "available soon" on that same Slack post. Salesforce's page is looser: it names ChatGPT among founding partners with Claude, Devin, Copilot, and Vercel, and says the connections work on any Slack plan. Until Slack's own availability line changes, treat ChatGPT as announced rather than confirmed live.

Do not read GitHub's Copilot Slack docs as a second launch. They describe the Copilot cloud agent integration — public preview, paid Copilot plans — that can start from a Slack thread or DM and open pull requests. Slack lists Copilot as a live Slack Code partner; GitHub is documenting how that agent behaves in Slack.

Vercel's day-one job is the preview loop. Slack says that inside a code channel, Vercel's agent kicks off a live preview the moment a change ships and posts a shareable link in the thread so the team sees the result before users do.

Salesforce says Slack Code itself is available on any Slack plan. Access to each partner agent is still required. The channel type does not replace a Copilot, Claude, Devin, or Vercel contract.

Keep the work in the open

Rob Seaman, EVP and GM of Slack at Salesforce, put the thesis this way: "AI only creates value when it's part of how a team actually works, not something people go do alone in another tab. Code channels bring that work into the open, where the rest of the team can see it, shape it, and build on it."

Slack is also rolling adjacent surfaces — agent DMs, a new Agents tab, and an Add to Slack path for third-party agents — and says the same model may later stretch beyond code. What is shipping for engineering teams now is the task-scoped, archivable code channel.

If you already have Claude, Devin, Copilot, or Vercel in Slack, mention the agent on a bounded bug or UI tweak and see whether a code channel appears. Walk one change through an in-channel diff and preview, and confirm who has to approve anything that looks like a production push.