Loading today’s stories
Product4 distinct publishers3 min readUpdated
Slack Code makes coding agents taggable teammates. Your merge-approval policy is now overdue
Slack shipped agent-run code channels on every plan. The bug-to-ship path can now skip the human engineer, and only "high-stakes actions" are gated.
The Product Desk · Product desk
What happened
- Slack debuted a feature called Slack Code, which lets teams collaborate with software-building AI agents directly within group chats.
- Users can tag an agent when they need automated assistance; it then starts a new chat, automatically including all the relevant team members and the context it needs to complete the task.
- Slack's press release: "With Slack Code, when you have an idea or need to build a new feature, update a web page, or fix a bug, you simply tag in a coding agent like Anthropic's Claude or Cognition's Devin, and that agent then spins up a code channel to tackle the task... There, everyone has full visibility to the conversation, can audit code diffs, get live previews of the agent's output, give feedback, and approve the work before it ships."
- Slack Code will work with the AI agents available on Slack's marketplace, and Slack says agents from founding partners including Claude Code, Devin, Vercel Agent and GitHub Copilot will integrate with code channels.
- Slack Code is available starting today on any Slack plan.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
Slack has launched Slack Code, a feature that turns software-building AI agents into taggable participants inside team channels: tag an agent and it spins up a dedicated code channel, pulling in the relevant people and context to work the task in the open [1][2][3]. It is available immediately on any Slack plan, with founding-partner agents Claude Code, Devin, Vercel Agent and GitHub Copilot, plus other agents from Slack's marketplace [4][5].
The consequence is in the routing, not the code generation. Gizmodo describes the intended flow plainly: a project manager who hears about a bug from a colleague can tag Claude Code, Devin, GitHub Copilot or a similar agent and have the fix built and shipped without waiting for a human engineer who may be busy with something else [6]. That is a ticket-to-production path in which no engineer is structurally required to appear.
Slack has put a gate on it. Company spokesperson Gianna Dimick told Gizmodo that Slack Code requires human sign-off on high-stakes actions such as merging code to production, governed by Slack's built-in enterprise security model [7]. In its press release, Slack says everyone in the channel can audit code diffs, get live previews of the agent's output, give feedback, and approve the work before it ships [3]. The channel then archives itself when the job is done and leaves an audit log for recordkeeping [10][11].
Read those two statements together and the gap is a matter of who, not whether. The sign-off is described in terms of the team approving [3][10]; nothing in the press release quote or the spokesperson statement, as reported, defines which humans are qualified to give it [13]. In a channel deliberately populated by the project manager, the requester and whoever else got auto-invited, "the team approved" and "someone competent read the diff" are not the same event. Gizmodo's own aside is the reason this matters: agents are prone to misinterpreting instructions and deleting codebases [8].
Slack is explicit that the silo is the thing it is removing. "This isn't your traditional coding experience, with one person and one agent working in a silo on their own," said Katie Steigman, Slack VP of product, in the demo video. "In the Code channel, the whole team and the agent work together on the build" [9]. Marc Benioff, whose Salesforce acquired Slack in 2020, posted the demo on X on August 20, 2026 with the line "Humans and agents. Same channel. Same work" [12][14].
So write the policy before the first channel opens. Name which repositories and environments are eligible; name the roles whose approval counts on a merge and whether a PM's thumbs-up qualifies; decide whether the gating that Slack applies to founding-partner agents also holds for arbitrary marketplace agents [4][7]; and confirm where the audit log lands and how long it is retained, given the channel deletes itself from view on completion [10][11].
What to watch: whether Slack's sign-off requirement is role-aware or merely human-aware, how the diff-and-preview review surfaces behave on changes bigger than a web page [15], and whether teams keep the archived channels discoverable when the first agent-shipped change needs a post-mortem.
Loading topic controls
Loading related stories