Slack Code for developers
By Steven Van ·
Agents can create dedicated channels from existing conversations, share progress and artifacts, then archive them with a summary.
Agents can now move multi-step work from an existing conversation into a dedicated code channel in Slack. Slack Code gives agents and human collaborators a shared place to review progress, discuss changes and inspect the work produced.
From a request to a working session
An app can create a code channel when a request involves back-and-forth, code changes, builds, tests or a pull request. When it supplies the original channel and message without overriding privacy, Slack matches the source channel’s privacy, lets its members join and keeps a link to the triggering message.
Inside the code channel, agents can reply directly in the channel and respond to messages directed at them without requiring a fresh mention each time. Top-level streaming messages are also supported.
Progress and artifacts beside the conversation
Apps can pin up to five context items at the top of the channel, such as a repository, branch, pull request, CI status or token usage. They can update these as work progresses and add tabs containing code diffs, canvases, Block Kit surfaces or HTML output.
Session status can show when an agent is processing, has finished a turn or is waiting for an answer. If the user stops the agent, the app receives a stop event and must immediately cease work for that session.
Closing the channel
When work is complete, the app can post a final summary and archive the channel. Slack records that message as the channel’s summary. The code channel lifecycle guide details the APIs developers use to manage the workflow.