Slack launches code channels—but only AI agents can create them

Slack introduced Code channels, a fresh approach to organizing agent-driven development work within its platform. When a supported coding agent determines a request warrants code implementation, it automatically creates a dedicated Code channel to house the entire working session—plan, repository branch, code changes, PR details, and live HTML output—rather than scattering the conversation across threads or general channels.

Team members viewing the channel can request adjustments or halt the agent's work. Upon completion, the agent archives the channel, which remains available for searching and serves as an audit trail of what was built and why.

The capability supports agents from Anthropic (Claude), Cognition (Devin), GitHub (Copilot), and Vercel, with OpenAI's ChatGPT arriving later. It rolls out to all Slack workspaces at no additional cost.

Why a new channel type was needed#

Slack already offers threads for lightweight agent conversations and regular channels for team collaboration. But neither maps well to a coding session, according to Katie Steigman, Slack's vice president of product.

Threads become unwieldy as agents perform extended work and more humans join to oversee or comment. Traditional channels, by contrast, feel too durable for temporary agent tasks—they're designed as permanent team spaces, not ephemeral coding sessions.

Code channels split the difference: they have a defined lifespan and inherit the visibility (public or private) of wherever the agent was invoked, but they're lightweight enough to be archived once the work wraps up.

How it works#

Code channels aren't a new AI model, runtime, or agent framework. Instead, Slack built an API that partner agents use to spin up and manage the channel type. Currently, access is limited to launch partners, with plans to broaden it later.

The integration doesn't rely on Model Context Protocol (MCP) or Agent2Agent (A2A) standards, though Slack does operate an MCP server for other integrations. Notably, humans cannot yet manually create Code channels—only agents can. Steigman left open the possibility this constraint could lift in the future.

Control and safety#

Agents inherit Slack's existing permission framework. Sensitive actions, like merging a pull request, still require human approval; the agent prepares the work, but a developer signs off before it ships.