Slack Code Opens Agent Work to the Team—but Rollout Is Still Gradual

Slack’s August 31 feature drop brought Slack Code into its latest product release, moving supported coding-agent sessions from individual tabs into dedicated channels where teammates can see conversations, code diffs and live previews, offer feedback and sign off on work.

The basic workflow is already defined: mention a supported agent in a channel or direct message, ask it to start a code channel and describe the task, then open the channel and add the people who need to review or steer the result. However, Slack’s current operating guide labels availability as a gradual rollout, so even an otherwise eligible workspace may not yet show the feature.

What a code channel exposes to the team

A code channel is a temporary, task-specific space managed by an agent. Instead of one user relaying prompts and screenshots, channel members can follow the same conversation, provide files or links as context and direct the agent in natural language.

The channel’s Artifacts area can show a code diff, a canvas, live HTML or a collected list of shared files and links. The precise names and contents depend on the agent. When code is available, reviewers can comment on individual lines or group several comments into a review that is sent back to the channel.

Visibility does not automatically grant every workspace member access. A public code channel is open for workspace members to join; a private one initially admits members of the conversation from which it was created. A channel member can then add other people or agents, within the workspace’s existing controls.

How to create the first code channel

The shortest first-session sequence starts in a conversation where an approved agent is already present:

1. Open a channel or direct message containing the supported agent, or add the agent to a channel.
2. Mention the agent, ask it to start a code channel and state the specific task.
3. Open the link the agent returns. On desktop, the session should also appear in the Code channels section of the sidebar.
4. Add teammates who need to contribute context, review artifacts or approve the output.

The agent normally creates the channel and derives its name from the initial request. Desktop users may also initiate a channel from Agents & tools, but the resulting space remains tied to one agent session rather than becoming a conventional permanent project channel.

The initial prompt should identify both the intended result and the scope. For example, a team could ask for a reviewable fix to one interface defect and name the relevant repository or component. Whether the agent can actually read or modify that repository still depends on the agent provider’s credentials and permissions.

How teammates review, redirect and approve work

Every participant in the session can suggest changes, inspect visible output and sign off on the result. That makes prompts, revisions and review discussion observable in one place, but a Slack sign-off should not be assumed to replace a repository’s merge rules or another system’s approval requirements.

Each session can display a status supplied by the agent: Working, Idle, Needs attention, Done, Inactive or Archived. These labels distinguish active generation from a session waiting for human input and allow members to monitor several agent tasks from the sidebar.

On desktop, a participant can hover over the Working badge and use the stop control when a response is taking too long or heading in the wrong direction. The team can then enter a revised prompt. This pauses the current response; it does not approve the output, revoke the agent’s access or close the channel.

Supported agents, plans and permissions remain the limits

Slack access and agent access are separate. The current approved list contains Claude from Anthropic, Devin from Cognition, GitHub Copilot and Vercel. Code channels are listed for all Slack subscriptions when a supported agent is installed, but the provider may require a separate paid account.

ChatGPT appears in Slack’s broader August 31 release messaging, but it is not on the approved-agent list in the current help article. That difference makes the list visible in the workspace—and the provider’s own availability terms—the safer operational test while rollout continues.

Provider-specific controls can narrow access further. For example, GitHub’s Copilot release note describes its Slack integration as a public preview for Copilot Business and Enterprise organizations, with administrator enablement, existing usage entitlements and repository permissions still applying.

Agents must also be installed through the Slack Marketplace. Code channels use Slack’s regular visibility and trust foundation, but that does not give an agent new rights in a connected repository, deployment platform or other external service. Administrators still need to verify the app installation, provider license and underlying resource permissions.

Closing a session does not necessarily erase it

Finishing the task presents two distinct controls. The close icon dismisses the code channel from the sidebar, while archiving leaves its messages available to view and search but prevents new messages and prompts.

An inactive code channel is removed from the sidebar automatically after seven days. That is a navigation rule rather than an immediate deletion of the conversation. Teams that need an explicit final state can archive the channel after review instead of waiting for it to disappear from the sidebar.

Slack Code therefore has a defined collaborative workflow, but not universal access: supported agents can create shared sessions, teammates can inspect and redirect their work, and completed records can remain searchable. The unresolved questions are when the controls will reach every workspace and when the operational agent list will expand to match Slack’s broader release messaging.

Also read:

• OutSystems Adds AI Agents, but Platform Commitment Still Sets the Limit
• AI Agents for Business, Not Demos: How Selleo Approaches Agent Development
• Figma’s Design Agent Is Open Beta—Paid Access Still Has Boundaries