Slack Code: Where Your Team and Agents Build Together | SlackSkip to main content

Get started

Close NavigationClose Navigation

Table of ContentsTable of Contents

7 min read<br>The real work has never been the document, the pull request, or the final build. It’s the conversation that gets you there, the back-and-forth, the pushback, the half-formed idea a teammate catches and turns into something brilliant. A brief, a deck, a block of code: they’re just proof that the real thinking already happened, together. We’ve believed this since Slack started, that work is better done in the open, in channels, not alone behind a closed door and revealed only once it’s “done.”

AI agents haven’t always been part of that. Usually, someone opens a private tab, prompts an agent, and disappears for a while, building in isolation, one person and their agent. The rest of the team finds out after the fact, with no chance to weigh in, catch a wrong assumption, or add context only they had. It’s a single-player game, and single-player games don’t scale: no pushback, no collision of ideas, just a fast way to get more of the same thinking. It’s the exact thing we’ve spent years building Slack to avoid, now happening again with agents instead of people.

Welcome to Slack Code

Slack Code brings software development out of private tabs and into the open, so your team and its agents can plan, write, and review together. It provides a dedicated space, called a code channel, that shapes itself around the work. Mention a coding agent on a complex project, and one spins up, pulls in anyone on your team, and the agent builds the space around what you need, like a code diff, a planning doc, or a live HTML preview. When the work’s done, the channel archives itself but remains like an audit log in Slack for future reference. That’s the shift Slack Code is built for: connecting what you’re building to the conversation your team is already having, in one place.

We’re starting with engineering because it’s the work closest to our hearts, the thing we live and breathe every single day. Today, we’re launching alongside Anthropic, Cognition, GitHub, OpenAI, and Vercel, with more partners joining us on the way.

Slack is a strategic part of a broader GitHub promise: humans set direction, agents close the loop. That has to be true wherever developers are working, which is why we're bringing Copilot into the flow of conversation in code channels to help teams turn shared intent into shippable software.

Why we built Slack Code

We didn’t design code channels in a vacuum, we built them out of sheer necessity for our own team. As our engineers leaned harder on coding agents internally, we hit a wall: squeezing complex, multi-turn agent execution into a standard channel thread felt cramped and noisy, but letting developers retreat into private browser tabs meant losing the thing that makes Slack work: everyone working in the open.

We realized agents didn’t need another isolated browser tab or terminal. They needed a seat at the table: a dedicated space that could expand when the project got complex, pull in the right humans at the right moment, and fade away when the job was done. Bringing teammates and agents into that same space has made building feel human, transparent, and genuinely fun, and the impact shows up in the numbers, too. One of our engineers put it simply: bug reports and small UI tweaks used to get filed away and forgotten. Now he spins up a side conversation right where the work’s happening, deals with it on the spot, and gets back to building.

Over 70% of code channels spin up and close within a single day, from idea to merged PR. Engineers get unblocked sooner, reviews need less context, and work just ships faster. That’s because the real value of AI doesn’t come from someone working faster in isolation. It comes from agents and teams building together at the speed of conversation. For the first time, an agent can build alongside your team in real time, with your teammates’ eyes on the work as it happens. It’s not solitary, it’s multiplayer, the exact same way your best work already is

Built for Code, Not Just Conversation

Threads work great for quick questions and updates. But working with agents to test a fix or catch a bug before it ships, needs more room to work. Slack Code gives agents and engineers that space, right where the coding happens:

A dedicated space per project. Mention an agent on real work, and a code channel spins up around that specific task, visible to the whole team, not just the person who kicked it off. It archives automatically when the work’s done, so nothing sprawls, but everything stays searchable.

See the code as it’s built. Code diffs, and live previews show up right in the code channel, not a wall of text. Catch a bug before it ships, flag a constraint before the agent runs with it, or pause and redirect mid-task.

Enterprise trust, no extra setup. Slack Code inherits Slack’s existing...