Slack on August 20, 2026 launched Slack Code, a feature that gives teams dedicated channels for building software alongside AI coding agents, available on any Slack plan from the same day. Rather than delegating a task to an assistant in a private chat, a team tags a coding agent such as Anthropic’s Claude Code or Cognition’s Devin into a conversation, and the agent opens a project-specific code channel where everyone can follow the work, review its output, and sign off before anything ships.
The code channels are open and project-specific, with dedicated tabs for each participant. Team members in the channel see the same conversation the agent is working from, can audit code diffs as changes are proposed, get live previews of HTML output, leave feedback the agent incorporates, and approve the finished work. When an assignment completes, the channel archives itself automatically, and each channel maintains an audit log for record keeping.
“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,” Slack said in its launch announcement.
Slack Code works with the AI agents distributed through Slack’s marketplace, and Slack said agents from its founding partners (Claude Code, Devin, Vercel Agent, and GitHub Copilot) will integrate with code channels. Availability on every plan, free workspaces included, puts the feature in front of Slack’s full user base at launch rather than gating it behind enterprise tiers. Slack is pitching the arrangement as working with agents the way teams already work with colleagues, in shared channels where the context for a task already lives.
How Slack Code Channels Work
The unit of work in Slack Code is the channel, not the chat window. A feature request, a bug report, or a page update becomes a task when someone tags an agent; the agent then creates a channel scoped to that task and begins working in it. Every step stays visible to the humans in the room, and the approval step is the control point: code does not ship until a person in the channel approves it. The self-archiving behavior keeps finished work from cluttering the workspace, while the audit log preserves who asked for what, what the agent changed, and who approved it.
The approach productizes what the industry has taken to calling vibe coding — describing software in plain language and letting a model write the code — inside an enterprise collaboration tool rather than a standalone builder. Startups such as Lovable have built entire platforms on that pattern, and Port has applied it to platform engineering. Slack’s version bets that the natural home for agent-written code is the workspace where engineering discussion already happens, the same environment where vendors like Harness are deploying agents for the surrounding development workflows.
The Platform Build Behind Slack Code
Slack Code arrives on top of more than a year of agent infrastructure shipped by Slack and its parent company, Salesforce. On December 9, 2025, Anthropic introduced a research preview letting developers delegate tasks to Claude Code directly from Slack threads, pulling context from bug reports and feature requests into coding sessions. Salesforce’s newsroom framed that preview as an early signal of Slack becoming what Ryan Gavin, Slack’s chief marketing officer, called “the future of work, where humans and AI agents partner in real time,” and noted that OpenAI, Google, Perplexity, Writer, Dropbox, Notion, Cognition, Vercel, and Cursor were all bringing agents to a Slack ecosystem of more than 2,600 third-party apps.
The plumbing followed. On February 17, 2026, Slack released its Model Context Protocol server and Real-time Search API, giving third-party agents secure, governed access to workspace channels, messages, and files. On June 18, 2026, the company introduced the Slackbot MCP Client, letting developers connect MCP servers directly to Slackbot so it could discover and invoke outside tools in conversation.
The day before the Slack Code launch, on August 19, 2026, Salesforce made the Slackbot MCP Client generally available as part of a broader Headless 360 platform expansion, connecting Slackbot to the Salesforce platform and more than 20 partner applications including Atlassian, Box, Canva, Docusign, Notion, and Zoom. Salesforce’s stated thesis in that release was that agents deliver the most value where employees already collaborate, and it named Slack as that surface.
Slack Code turns that plumbing into a shipping surface: the channel becomes the place where agent-written code gets reviewed, approved, and logged. The next concrete milestone is the arrival of the four founding partners’ agents inside code channels, which Slack has said will integrate with the feature.
Credit: Source link
