---
title: "Slack Code brings AI coding agents into Slack channels"
description: "Slack launched Slack Code on August 20, 2026: channels where Claude, Devin, Copilot or Vercel's agent code in front of your team. How it works."
url: "https://vibe-code.blog/en/slack-code-agent-channels"
lang: "en"
author: "Thierry Gustin"
published: "2026-08-25"
updated: "2026-11-21"
---

# Slack Code brings AI coding agents into Slack channels

> **Key takeaways** — On August 20, 2026, Slack launched Slack Code, "code channels" where a team hands a task to a coding agent (Claude, Devin, GitHub Copilot, Vercel's agent) and follows its plan, diff and live preview. The channels come with every Slack plan at no extra charge, but each partner agent is paid for separately. For vibe coders, it is mainly a way to get work reviewed by a team or client without a meeting.

**Slack Code** launched on August 20, 2026. Slack is not shipping its own coding agent: it creates dedicated channels where a third-party agent, such as Claude or GitHub Copilot, works on a task in full view of the team. Vibe coding becomes a group activity, with a history and human sign-off. Here is what was announced, who it is for, and how to use it without losing control.

## How does Slack Code work?

Slack Code turns an agent mention into a workspace. Slack's official post, by Katie Steigman and Claire Bowman, describes this flow:

1. In any conversation, you mention a coding agent with a task.
2. A **code channel** spins up around that task, visible to the whole team rather than just the person who started it.
3. The agent pulls in the right people and builds the workspace: a plan, a code diff, a live HTML preview.
4. Teammates follow progress, spot problems and redirect the agent mid-task. Anyone can pause, redirect or stop it.
5. When the task is done, the channel archives itself and stays searchable as an audit log.

According to The Next Web, each channel has four tabs: conversation, plan, code diffs and live preview. Slack says high-stakes actions, such as merging code to production, require human sign-off right in the channel.

> Nobody's out of the loop, nobody needs an extra meeting.
>
> — Katie Steigman, Slack VP of product, quoted by Gizmodo and The Next Web

## Which agents work with Slack Code?

At launch, four integrations are live and a fifth is announced for later.

| Partner | Agent | Status on August 20, 2026 |
| --- | --- | --- |
| Anthropic | Claude | Live |
| Cognition | Devin | Live |
| GitHub | [GitHub Copilot](https://github.com/features/copilot) | Live |
| Vercel | [Vercel](https://vercel.com/)'s agent | Live |
| OpenAI | ChatGPT | "Available soon" |

Slack's post gives concrete examples: Vercel's agent starts a live preview when a change ships and posts the link in the thread; Devin reports back with a working preview after fixing a bug; the GitHub integration lets you tag an engineer to review a draft fix.

Separately, an "Add to Slack" flow lets you connect agents built with other tools, including [Lovable](https://lovable.dev/) and [n8n](https://n8n.io/), according to Salesforce's product page and The Next Web.

## How much does Slack Code cost?

Code channels are included in every Slack plan at no extra charge, according to The Next Web and Salesforce's page. You do need access to each partner agent, billed by its own vendor. Salesforce adds that availability varies by region and that pricing and packaging may change. In practice, Slack Code costs nothing more if you already pay for Claude, Copilot or Vercel; it does not replace any of those subscriptions.

> **What Slack Code is not** — Slack Code is not a coding agent. It is a collaboration and oversight layer around existing agents. Code quality still depends on the agent you pick.

## Why does this matter for vibe coders?

Vibe coding has a well-known flaw: you do it alone, in a browser tab, and nobody sees what the AI changed until something breaks. Slack Code goes straight at that problem. The plan, the diff and the preview are visible to the team, and the history sticks around.

Three cases where that makes a real difference:

- **Freelancers or agencies with a client on Slack**: the client watches the live preview and approves in the channel, no demo call needed. Our pieces on [selling vibe-coded apps to clients](https://vibe-code.blog/en/freelance-vibe-coding) and showing a working prototype at the first meeting make the same point.
- **Small non-technical teams**: the marketing lead asks for a page, the agent builds it, and someone qualified reviews the diff before it goes live.
- **Traceability**: the archived channel is your memory. When a bug shows up three weeks later, you can see who asked for what and what the agent changed.

To understand what an agent is actually doing when it "works" in a channel, read our explainer on AI coding agents and subagents.

## What risks should you watch?

The main risk is mistaking visibility for verification. Seeing a diff in a channel does not mean anyone understood it. If nobody on the team can read code, human sign-off turns into clicking "OK".

Two more points:

- **An agent that reads a channel reads everything posted in it.** A malicious message, link or pasted file can carry hidden instructions. Our article on prompt injection explains how that works.
- **Inherited Slack permissions** are convenient, but check what each agent can actually do in your repository and hosting. Slack controls who sees the channel, not what the agent is allowed to push.

## How do you try it safely?

Start small, on a low-stakes project, with clear guardrails.

1. **Pick one agent** you already pay for and connect it to your Slack workspace.
2. **Set up a branch or a staging environment** before the first task. Our guide to staging and backups shows how to never touch the live version.
3. **Name a reviewer** who can read a diff, even roughly. Our method for [testing AI-generated code when you are not a developer](https://vibe-code.blog/en/testing-ai-generated-code) gives a simple checklist.
4. **Keep Git as your source of truth**: the channel is a log, not a backup. See our guide to [Git for vibe coders](https://vibe-code.blog/en/git-for-vibe-coders).
5. **Write a precise task** with acceptance criteria.

A message template to post in Slack to kick off a clean task:

```
@agent Task: add a contact form to the /contact page.
Criteria: name, email and message fields; server-side validation;
no API keys in the front end; live preview before any merge.
Do not merge anything into main without approval from @reviewer in this channel.
```

> **The right setting** — Write "nothing goes to production without human approval" into the task itself, even though Slack provides for it. An agent follows an explicit instruction better than a setting it cannot see.

## Frequently asked questions

## Frequently asked questions

### Is Slack Code free?

Code channels are included in every Slack plan at no extra charge, according to The Next Web and Salesforce's page. You still pay for access to each partner agent through its vendor, for example Anthropic for Claude or GitHub for Copilot. Salesforce notes that availability varies by region and that pricing may change.

### Which coding agents can I use in Slack Code?

At launch on August 20, 2026, Slack named Anthropic's Claude, Cognition's Devin, GitHub Copilot and Vercel's agent. OpenAI's ChatGPT is listed as "available soon". An "Add to Slack" flow also lets you connect agents built with other tools such as Lovable or n8n.

### Does Slack Code replace Cursor or Claude Code?

No. Slack Code does not write code itself: it hosts third-party agents in shared channels. If you work alone, your editor or terminal agent is still more direct. Slack Code earns its place when several people need to follow, redirect or approve an agent's work.

### Can an agent push code to production without approval?

Slack says high-stakes actions such as merging to production require human sign-off in the channel. That safeguard depends on each integration's setup and on your repository permissions. Protect your main branch on GitHub and spell out the rule in every task you give the agent.

### Can my client follow the work in Slack Code?

Yes, if they have access to the channel. The code channel shows its members the plan, the diff and the live preview, which is handy for getting a mockup approved without a meeting. Just make sure the channel holds no secrets or other clients' data before you invite them.

## Sources

- [Slack Code: Where Your Team and Agents Build Together — Slack (August 20, 2026)](https://slack.com/blog/news/slack-code-channels-for-agents)
- [Introducing Slack Code — Salesforce](https://www.salesforce.com/introducing-slack-code/)
- [Slack launches Slack Code, where teams and AI agents build together — The Next Web](https://thenextweb.com/news/slack-code-ai-coding-channels-launch)
- [Slack Has (of Course) Launched a Vibe Coding Tool — Gizmodo](https://gizmodo.com/slack-has-of-course-launched-a-vibe-coding-tool-2000800885)
- [Slack Launches Code For AI Coding Collaboration — Dataconomy](https://dataconomy.com/2026/08/21/slack-launches-code-for-ai-coding-collaboration/)

— Thierry Gustin, Formateur en intelligence artificielle (GustinAI) · November 21, 2026
