Slack Wants to Be the Shared Desk for Rival Coding Agents

Slack is turning the engineering conversation into a work queue for coding agents. Slack Code, announced by Marc Benioff on August 20, places agents from Anthropic, GitHub, Cognition and Vercel in shared Slack channels where teams can assign tasks, follow replies and see work status. The launch was being demonstrated at Dreamforce 2026, and Benioff said all four integrations were live.

The important distinction is architectural. Slack Code presents a common conversation surface, not a common execution environment or model layer. Each provider still brings its own agent, customer relationship and underlying development infrastructure. Slack’s role is to collect the request, the agent’s progress and the human response in the same place.

The integrations bring together tools that had already established distinct roles in Slack. GitHub’s Copilot coding agent can take a bug fix, test task or refactor from a Slack thread and return a link to a prepared pull request. Anthropic’s Claude Tag, introduced in June, gives selected channels a shared Claude identity that can retain channel context; its beta initially targeted Claude Team and Enterprise customers.

The division of labor behind the shared channel

• GitHub supplies a route from a discussion to repository work and a proposed pull request.
• Anthropic supplies a shared channel-based Claude identity with retained conversation context.
• Cognition’s Devin can be tagged on bug reports or feature requests, then return code or a pull request; Cognition tells customers to review its output.
• Vercel connects Slack events and approval steps to execution environments and Vercel deployments.

That division helps explain the product’s pitch. A feature request or bug report can begin in the discussion where its intent and tradeoffs are already being debated, then move to an agent without a separate handoff. GitHub handles repository work, Vercel can connect the workflow to approvals and deployment, while the channel keeps the requesting team in the loop. Slack is packaging those previously separate paths under one coordination layer.

A shared channel also becomes a permissions boundary. Coding agents may need access to repositories, credentials and execution environments, while Slack conversations can be public, private or direct. Administrators therefore need to decide which conversations may trigger work and which actions require approval. That question is especially consequential when a chat request can lead beyond a draft response toward code changes or deployment activity.

For Salesforce, which acquired Slack in 2021, Slack Code extends Slack’s developer role without requiring Salesforce to build every coding agent itself. Anthropic, GitHub, Cognition and Vercel can continue selling their own agent, repository and deployment products while Slack becomes the shared front door. The unresolved test is whether teams will prefer that common channel when the systems doing the work remain independently operated and governed.