Slack Code is a feature Slack launched on August 20, 2026 that turns an AI coding task into a dedicated Slack channel. Inside that channel a connected coding agent posts its plan, the code it wrote, previews and test results, and teammates comment and approve before the work ships. The idea is to move agent work out of one engineer's terminal and into a shared, searchable space where designers, product managers and reviewers can see it.

Which AI coding agents work with Slack Code?

At launch Slack named partner integrations with Anthropic's Claude Code, GitHub Copilot, Cognition's Devin and Vercel's agent. Slack supplies the channel, the approval surface and the audit trail; the partner supplies the agent that actually reads and writes code.

How much does Slack Code cost?

Slack has positioned the code channels themselves as available across Slack plans, including free workspaces, at no additional charge. You still pay each agent vendor separately for the agent — a Claude, Copilot or Devin subscription — and the broader Slack AI add-on for search, summaries and digests is a separate paid product listed at roughly $10 per user per month on Pro and Business+ tiers.

Is Slack Code a replacement for Claude Code or Cursor?

No. Slack Code does not include its own coding model or agent. It is a coordination and approval layer that sits in front of agents you already pay for, so it competes with GitHub pull request review and ChatOps workflows rather than with the agents themselves.

Quick Answer

What Is Slack Code? AI Agent Channels Explained 2026

Published: August 21, 2026

The Short Answer

Slack Code, announced August 20, 2026, turns a single AI coding task into a dedicated Slack channel. The agent works inside that channel: it posts its plan, shows the diff, renders a preview, and waits for a human to approve before anything ships.

It does not ship an agent of its own. Slack sells the room; you bring the worker.

	Slack Code
Launched	August 20, 2026
What it is	Shared channel per coding task
Agents supported	Claude Code, GitHub Copilot, Devin, Vercel agent
Who approves	Humans, in-channel, before merge
Cost of the channels	No additional charge, including free workspaces
What you still pay for	The agent subscription, separately

What Problem It Actually Solves

Agent work today is invisible to everyone except the person who launched it. An engineer runs Claude Code or Devin in a terminal, iterates for forty minutes, and the rest of the team sees one pull request with no record of what was tried, what was rejected, or why.

That is fine when one person owns one change. It breaks in three specific places:

Review — a reviewer sees the destination, never the route.
Non-engineers — a designer or PM who could have caught a wrong assumption at minute three finds out at minute forty.
Audit — when something goes wrong, “what did the agent do and who said yes” has no home.

Slack Code answers all three by making the channel the unit of work rather than the branch. The transcript is the audit log, and it is searchable with the same tools your team already uses for everything else.

How a Slack Code Channel Works

The flow Slack describes is deliberately linear:

Kick off a task — describe the work; Slack creates a channel scoped to it.
The agent plans — it posts its intended approach before touching code, so a human can redirect it early and cheaply.
The agent implements — file changes and diffs appear in-channel as it goes.
Preview — where the connected stack supports it, a running preview of the change is linked in the channel.
Approve or reject — a human gates the merge. Nothing ships on the agent’s own authority.

The important design choice is step 2. Redirecting an agent at the plan stage costs a sentence; redirecting it after implementation costs the whole run. Putting the plan in a room where four people can see it is a cheap way to catch the expensive error.

Which Agents Connect

Slack launched with partner integrations rather than a house model:

Claude Code (Anthropic)
GitHub Copilot (Microsoft/GitHub)
Devin (Cognition)
Vercel’s agent

That list is strategically interesting: it is four direct competitors sharing one surface. Slack is betting that the coordination layer is a defensible position even when it owns none of the intelligence — the same bet Slack originally made against email.

What It Costs

The code channels are positioned as available on any Slack plan, including free workspaces, at no additional cost. There are two separate bills to keep in mind:

The agent — you need your own Claude, Copilot, Devin or Vercel access. Slack does not resell it.
Slack AI — the broader add-on covering AI search, conversation summaries and daily digests is a distinct paid product, listed at around $10 per user per month on Pro and Business+ when billed annually, with custom pricing on Enterprise Grid. It is not required to use code channels.

The free-tier positioning is the aggressive part. Slack is optimising for adoption surface, not for direct revenue on this feature.

Where It Fits — And Where It Doesn’t

Use it when review, approval and visibility are the bottleneck. Teams with designers and PMs who need to see work in progress, regulated environments that need an approval trail, and distributed teams already living in Slack get the most from it.

Skip it when you are one or two engineers moving fast. The channel-per-task model adds ceremony that only pays off when there is an audience. A solo developer with Claude Code in a terminal is strictly faster.

The honest limitation: Slack Code inherits whatever your agent can and cannot do. It makes agent work legible; it does not make it better. A bad plan reviewed by four people in a channel is still a bad plan — it just fails earlier and more publicly, which is genuinely worth something.

The Bigger Pattern

Slack Code landed in a four-day window with two other launches solving the same problem from different angles: Cursor Origin (August 17, 2026) pulled code hosting into the editor, and Warp Factories (August 18, 2026) opened a closed beta for model-agnostic agent infrastructure.

Three vendors, one week, one question: where does agent work live now that the terminal is too small for it? Slack’s answer is the channel you already have. Cursor’s is the editor. Warp’s is a control plane you build. Nobody has been proven right yet, which is exactly why the question is worth watching.