Omniscio

OmniscioGuidesClaude Code in Slack

Claude Code in Slack: delegate a task from a channel

Claude Code in Slack is the shortest road from a conversation to a commit. Somebody describes a bug in a channel, Claude answers it as a cloud session, and the work happens on a branch while the thread keeps its own record of what was asked.

This page covers what the integration needs, the five setup steps, the two routing modes, what each person's account can reach, and the notices that appear instead of an answer.

Last checked against Anthropic's Claude Code documentation on November 18, 2026. By the Omniscio team. Updated .

What it is, and which version you have

When you mention @Claude with a coding task, the integration detects the intent and creates a Claude Code cloud session, so the work happens without leaving the thread. It is built on the existing Claude for Slack app and adds routing to Claude Code sessions.

There are two versions, and which one a workspace gets is not the individual user's choice. This page covers the earlier one: it answers channel mentions only from Pro, Max and Ultra accounts, and only in a workspace no organization has connected to Claude Tag. Claude Tag is Anthropic's Team and Enterprise product, where @Claude acts as the organization's shared identity with admin-configured access.

That split explains almost every confusing reply. On Team or Enterprise your workspace already has Claude Tag, so the earlier behaviour is not available there at all, and the notice you get says so.

Sources: "Claude Code in Slack" intro and its warning box in Anthropic's Slack page, read November 18, 2026.

What it needs first

Five requirements, and a missing one shows up as a notice rather than a working setup:

  • A Pro, Max or Ultra plan.
  • A Slack workspace not connected to Claude Tag. If @Claude replies with the retirement notice, the workspace is connected.
  • Cloud sessions enabled for your account.
  • A GitHub account connected at claude.ai/code, with at least one repository authenticated.
  • Your Slack account linked to your Claude account through the Claude app.

Source: "Prerequisites" in Anthropic's Slack page, read November 18, 2026.

The five setup steps

Two of the five are the admin's and three are yours, which is why a setup that only half happened looks like a permissions bug.

  1. A workspace administrator installs the Claude app from the Slack App Marketplace and clicks Add to Slack.
  2. You connect your Claude account: open the Claude app in Slack, go to the App Home tab, click Connect Claude account, and finish in the browser.
  3. You configure cloud sessions: sign in at claude.ai/code with the same account, connect GitHub, and authenticate at least one repository.
  4. You choose a routing mode in the App Home. The next section covers the two.
  5. You invite Claude to the channels you want it in with /invite @Claude. Installation adds it to nothing.

Source: "Setting up Claude Code in Slack" in Anthropic's Slack page, read November 18, 2026.

Two routing modes

The Routing Mode setting in the Claude App Home decides what an @mention means.

  • Code only sends every mention to a Claude Code session. Right when the workspace uses Claude in Slack for development and nothing else.
  • Code + Chat reads each message and routes it: coding tasks to Claude Code, writing and analysis and general questions to Claude Chat.

The misroute has an escape hatch. If Claude answers in Chat when you wanted a session, click Switch to code repo... on the reply and pick a repository; Claude starts a Claude Code session with the message you already wrote.

Source: "Choose your routing mode" and "Message actions" in Anthropic's Slack page, read November 18, 2026.

What happens after the mention

The session runs on claude.ai/code, and the thread becomes a status feed for it. Anthropic's sequence is worth knowing because it explains what the thread will and will not contain:

  1. You mention @Claude with a coding request.
  2. Claude detects the coding intent.
  3. A session is created on claude.ai/code.
  4. Progress updates appear in your Slack thread.
  5. When it finishes, Claude edits its message with the final answer and action buttons, and sends you a direct message linking to it — a notification; Claude Code still takes work only from channels.
  6. You click View session for the full transcript, or Create PR to open the pull request.

Context comes from the conversation. In a thread, Claude reads your messages and its own; mentioned directly in a channel, it also reads recent messages and the channel's name, topic and description. If a teammate's error report matters, paste it into the message where you mention Claude rather than assuming it was read.

That context is also the security model, and Anthropic states it plainly: Claude is given access to the conversation context, so it may follow directions from other messages in it. Use it in conversations you trust.

Sources: "Session flow", "Context gathering" and "Repository selection" in Anthropic's Slack page, read November 18, 2026.

Whose account, whose limits

Every session runs under the account of the person who mentioned Claude, and everything follows from that: it counts against their plan limits, it can reach only the repositories they connected, and it appears in their own history at claude.ai/code.

Access is narrowed at two more levels. A workspace administrator decides whether the app is installed at all, and removing it revokes access for everyone in that workspace immediately. And because installation adds Claude to no channels, an admin can control who uses it by controlling which channels it is invited to and who can see those channels.

On Enterprise and Team accounts, sessions created from Slack are visible to the organization automatically.

Sources: "Access and permissions" and "What's accessible where" in Anthropic's Slack page, read November 18, 2026.

The notices that stop it

Three replies look like failures and are not. Each names its own cause.

  • "This workspace isn't set up for Claude Tag yet" appears when no organization has connected the workspace to Claude Tag and the Claude account you linked is not on Pro, Max or Ultra. Claude Tag is the Team and Enterprise product; the notice names an @Claude connect command to start with.
  • "The legacy Claude in Slack bot is retired" means your workspace is connected to a Claude organization and the earlier version is still selected for the channel, the workspace or the organization default. It does not depend on your own plan, so Pro, Max and Ultra accounts get it too. An Owner changes it in Claude's admin settings, or on the workspace or organization default to fix every inherited channel at once.
  • "Claude Code is not enabled for your account" means the account has no cloud environment yet. Sign in at claude.ai/code once with the same account and finish the web onboarding, which creates your default cloud environment or asks you to. Each person does this individually, and the error clears on the next mention.

Two smaller ones are worth the same treatment. Sessions that will not start usually mean the account is not connected in the App Home, cloud sessions are off, or no GitHub repository is connected. A repository that will not appear usually means it was never connected at claude.ai/code, or your GitHub permissions on it are missing.

Source: "Troubleshooting" in Anthropic's Slack page, read November 18, 2026.

What it cannot do

  • GitHub only. Repositories must be on GitHub.
  • One pull request per session.
  • No direct messages. Channels only, public or private.
  • No work without cloud sessions. The feature is a front door to them, not a separate runner.

For a job that needs files uploaded, or a long back-and-forth while it runs, Anthropic's own advice is the web interface rather than Slack. Slack is for starting a task asynchronously and letting teammates watch it happen.

Sources: "Current limitations" and "When to use Slack vs. web" in Anthropic's Slack page, read November 18, 2026.

Where these answers come from

Common questions

Does it work in direct messages?

No. Channels only, public or private, and only where Claude has been invited with /invite @Claude.

Whose usage does a Slack task consume?

Yours. Each person runs sessions under their own Claude account, on their own plan limits, with access to their own connected repositories.

Why did @Claude reply with a notice instead of doing the work?

Read the notice. It says which of the three applies: no Claude Tag setup on a non-Pro plan, a workspace connected to a Claude organization, or an account with no cloud environment yet.

Can one session open two pull requests?

No. One per session. Create PR opens GitHub's compare page for that session's branch, where you finish it.