Salesforce announced Slack Code on August 24, a feature that gives teams dedicated channels for working alongside AI coding agents, including Anthropic’s Claude Code, Cognition’s Devin, GitHub Copilot, OpenAI’s ChatGPT, and Vercel’s agents, rather than isolated browser tabs. Each code channel organizes the work into tabs for conversation, the agent’s plan, line-by-line diffs, and a live preview, so the whole team can watch an agent build in real time. Slack EVP and GM Rob Seaman framed the point of the feature directly: “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.”
Why it matters to enterprise AI buyers
The governance mechanics matter more than the multi-agent compatibility list. Anyone in a code channel can pause, redirect, or stop an agent mid-task, and human sign-off is still required before an agent’s changes reach production, with searchable audit logs and Slack’s existing security and admin permission model inherited automatically. That is a direct answer to a concern that has slowed agentic coding adoption inside larger, more regulated engineering organizations: an AI agent working in an individual developer’s private tool is invisible to the team until a pull request lands, by which point review happens after the fact rather than during the work. Putting the agent’s actual working process inside a shared, auditable channel turns AI-assisted development into something a tech lead or compliance function can observe continuously, not just gate at the end. For enterprise buyers evaluating agentic coding tools, whether a vendor treats “team visibility during the work” as a governance feature, not just a collaboration nicety, is becoming a real differentiator.
Source: Salesforce
