Slack Code is Salesforce's agentic coding surface for Slack: project-based "code channels" where a team and external coding agents (Claude, Devin, GitHub Copilot, ChatGPT, Vercel) plan, build, review, and ship together in one shared conversation. It packages the "agent in the chat room" pattern — previously bolted together per team via Copilot integrations or DIY agents — into a managed, multi-vendor platform.
Why It's in Assess
Slack announced Slack Code in late August 2026; general availability reportedly began August 20, 2026 with the formal launch press release following August 24, 2026. It is a genuinely new work surface rather than a feature tweak, which is why it warrants assessment rather than neglect:
- Code channels: Mention a coding agent (e.g. Claude Tag) on real work and it spins up a dedicated channel with separate tabs for the conversation, the agent's action plan, line-by-line code diffs, and a live preview of the running output. Channels archive themselves on completion but remain searchable as an audit log. Slack reports over 70% of code channels complete within a day (idea-to-merged-PR figures are vendor-sourced).
- Launch partner lineup: Anthropic's Claude Code, Cognition's Devin, GitHub Copilot, OpenAI's ChatGPT (phased), and Vercel agents are available on all Slack plans, with separate access to each partner agent required. The code-channel APIs are slated to open to custom enterprise agents later.
- Governance without new plumbing: Agents inherit Slack's existing security model, permissions, and admin controls, and human sign-off is still required before agents push to production — no separate IT approval pipeline for high-stakes actions. Anyone in the channel can pause, redirect, or stop an agent mid-task.
- Broader agent surfaces: The same release adds Agent DMs (real titles, agents clearly labelled), an Agents tab as a home base for managing sessions, and one-click "Add to Slack" distribution for agents built with NanoClaw, Lovable, n8n, LangChain, Runlayer, and others.
Assessment is warranted because the adoption evidence so far is largely Salesforce's own ("building in the open" internally, and launch-partner quotes), not independent production accounts. Teams should validate whether code channels genuinely beat threads-plus-private-tabs for their review and handoff flow, and weigh Slack as an additional dependency hub for agent-driven work, credential middleman for partner agents, data-residency posture, and per-agent billing complexity.
Key Characteristics
| Property | Value |
|---|---|
| Interface | Slack (code channels, agent DMs, Agents tab) |
| Provider | Salesforce (Slack) |
| License | Proprietary (Slack commercial terms) |
| Pricing | Included in Slack plans; requires separate access to partner agents |
| Partner agents | Claude (Anthropic), Devin (Cognition), GitHub Copilot, ChatGPT (OpenAI), Vercel agents |
| Sandbox | Inherits Slack's security model; human-sign-off gate before production push |
| Website | slack.com |