Slack opens its Code API to all developers who make AI agents

Slack made its Slack Code API available to all developers on all Slack plans. Before this, only a small number of partners could let an agent open a code channel, a shared Slack area for one task. More than 150 customers and partners asked for access. At this time an agent can open a channel, add persons and files, send updates and close the channel when the work is done.

How it works

An agent opens a code channel when a task is too large for a thread. Team persons can monitor the agent, add context and give approval for changes in Slack. Slack shows code diffs, HTML previews and thinking steps, and developers do not need to make their own screens. The agent keeps the permissions and the admin controls of its channel.

The proof

Slack gives one number: GitHub Copilot opens a code channel in 30% of its agent sessions. Slack gave no test results on speed or quality. The tools for pull requests on GitHub come after this, with no date.

What is not known

Slack says that IT has nothing new to set up and that each high-risk change can have the approval of a person. These are claims by Slack. It does not say how correctly agents from other companies work in code channels.

Insight: Chat and editor race to host agent work

Slack says users can change agents or models and stay in the same position. In September 2026, Microsoft VS Code 1.137 gave each agent its own container in the editor. This reads as a race to own the area where agent work, approvals and records stay, because that area makes agents easy to change. Leaders: the host that keeps your history is hard to change.