Slack Code introduces AI-assisted software development directly within team conversations, allowing developers to collaborate with coding agents in dedicated channels. This feature enables teams to follow task progress, review code changes, and provide feedback without switching between tools. Developers can initiate tasks, share files, and engage in discussions, enhancing collaboration and transparency. The Slack Code API also allows for custom agent integration, making it easier for teams to build tailored experiences. Overall, Slack Code streamlines coding workflows and fosters teamwork by keeping all relevant information and discussions within a single platform.
Slack is bringing AI-assisted software development into team conversations with Slack Code. It gives developers a shared space where they can ask coding agents to work on tasks, follow their progress, review code changes, and involve other teammates.
The idea is to make coding work easier to follow. Instead of an agent working in a separate chat or browser tab, Slack Code creates a dedicated channel where the agent and team can work on the same task. This can include fixing bugs, writing code, creating prototypes, and reviewing changes.
With its latest Code API, Slack is also allowing developers to connect their own agents to this experience. In this blog, we will look at what Slack Code does, how it works with AI agents, and what it means for developers using Slack.
What Is Slack Code?
Slack Code is a feature that brings AI coding work directly into Slack. It gives a coding agent its own dedicated channel to work on a task, so developers and other team members can follow what is happening without switching between different tools.
For example, a developer can ask an agent to investigate a bug or build a feature. The agent can work through the task, share its plan, post code changes, and provide a preview where supported. Teammates can join the channel, add context, review the changes, and give feedback along the way.
What makes Slack Code useful is that the coding work does not stay between one person and an AI agent. The rest of the team can see the progress, contribute to the discussion, and stay involved before the work moves forward.
How Slack Code Works
A team member mentions a supported coding agent in a Slack channel or direct message and describes the task. When the work needs more than a quick response, the agent can create a dedicated code channel.
The channel carries the original context forward. Teammates can join, share files, add instructions, and follow the task without moving between separate conversations.
Keep the work organised in one place
- Conversation: Teammates and the agent discuss the task.
- Plan: The agent shares the steps it intends to take.
- Code diffs: Developers inspect the lines that were added or changed.
- Live HTML preview: The team views prototypes or generated interfaces.
- Files and links: Shared project material stays accessible.
People can add feedback, comment on code, provide more context, or pause an agent if it is heading in the wrong direction. Available actions depend on the connected agent.
When the work is complete, the code channel can be closed or archived. Its messages and artifacts remain searchable, making earlier decisions and technical context easier to revisit.
What Developers and AI Agents Can Do Together
Slack Code is designed for tasks that need input from more than one person. A developer can ask an agent to investigate a bug, suggest a fix, or create a prototype.
For Slack AI agents, this creates a shared working space rather than a one-to-one prompt window. Agents can post progress updates and share artifacts while people guide the task.
Teams can use this setup for activities such as:
- Investigating bugs and reviewing possible fixes.
- Creating or updating code and sharing line-by-line changes.
- Building HTML prototypes and previewing the results.
- Bringing logs, files, and project details into one task.
- Coordinating code reviews and follow-up work with teammates.
Supported agents and integrations
Slack’s current Help Center lists supported apps including Claude, CodeRabbit, Datadog, Devin, Factory, GitHub Copilot, Lovable, Mistral Vibe, NanoClaw, Replit, Rhythms, and Vercel. Availability and account requirements can vary by app.
This partner ecosystem gives developers options instead of locking every team into one coding model. Slack Code also uses existing channel permissions and admin controls, keeping agent activity within the workspace’s access boundaries.
What Slack Code Means for Developers Building Their Own Agents
The Slack Code API became generally available on October 28, 2026, opening the experience to developers building custom agents. An agent can create a code channel, add relevant people and files, post updates, display artifacts, and manage the session.
For Slack for developers, this means teams can build their own agent experiences without creating every collaboration interface from scratch. The APIs support code diffs, HTML previews, and other structured content.
Organisations can connect an internal agent built for their own systems or create an app for the Slack Marketplace. Their teams can then work with those agents in the same familiar workspace.
Moving Your Team to Slack?
Slack Code is most useful when project conversations, people, and tools are already accessible in Slack. If your organisation currently works in Microsoft Teams or Google Chat, planning the move is an important first step.
The Slack migration process involves more than creating new channels. Teams need to consider existing messages, threads, files, user identities, channel membership, and permissions.
Move to Slack helps organisations transfer collaboration data from Microsoft Teams or Google Chat into Slack. Its migration workflow includes:
- Connecting the source workspace and reviewing its data.
- Mapping users, channels, conversations, and relevant permissions.
- Transferring messages, threads, files, and channel history into Slack.
The platform preserves threaded conversations and original timestamps. It also supports phased or delta migrations to reduce disruption, with the exact scope depending on the source workspace.
If your organisation is planning to migrate to Slack, Move to Slack can help with the transition. Book a call with the team to discuss your migration requirements and plan the next steps.
Wrapping Up
Slack Code brings developers, colleagues, and AI agents into one shared space to plan work, review code, and make decisions together. Teams can follow agent activity without stepping away from their own responsibilities.
As Slack continues to open its tools to custom agents, the way teams build and collaborate will keep evolving. With a considered Slack migration process and the right setup, organisations can bring their conversations and development work into one workspace.
Frequently Asked Questions
Slack Code gives developers a shared channel to assign coding tasks, track agent progress, review code changes, and collaborate with teammates.
Slack Code supports agents such as Claude, Devin, GitHub Copilot, CodeRabbit, Replit, Vercel, and Lovable, with availability depending on app and workspace requirements.
Yes, organisations can migrate messages, files, threads, and channel history from platforms like Microsoft Teams or Google Chat using a structured Slack migration process.
Slack for developers combines team communication and AI-assisted coding, allowing developers to manage tasks, review outputs, share technical context, and coordinate work in one workspace.
Businesses can use Move to Slack to transfer workspace data, map users and channels, preserve threaded conversations, and plan phased migrations with minimal disruption.