TL;DR Invite
@Claudeto the channel, connect your account and a repository at claude.ai/code, and mention it only in threads you trust. Thread context drives the repository choice and the approach.
The bug lands in Slack. The thread already has the stack trace, the repro steps, and three messages of context. Instead of pasting all of that into your terminal, you mention @Claude in that thread. Claude detects a coding task, opens a Claude Code session on the web, and works there under your account with your connected repos. Progress posts back to the thread; when it finishes, it mentions you with a summary and buttons to open the session or create a PR.
That is not the same as Channels (Telegram or Discord), which push events into your local session, and not the same as a Slack MCP server, which reads or writes Slack from the CLI. Here the source is the thread; the work runs in the cloud.
Here is the shape of the thread (a sketch; the buttons are the app's literal labels):
@Claude investigate the 500 on checkout and open a PR with the fix
Claude posts status to the thread while it works.
When it finishes it @mentions you with the summary and two buttons:
[View Session] [Create PR]
Setup
1. Install the Claude app in the workspace
A workspace admin installs the app from the Slack App Marketplace and adds it to Slack.
2. Connect your Claude account
In Slack, open the Claude app (Apps → Claude → App Home) and click Connect. Authenticate in the browser with the same account you use for Claude Code.
3. Prepare Claude Code on the web
Visit claude.ai/code once with that account, connect GitHub, and authenticate at least one repository. Without a cloud environment you will see "Claude Code is not enabled for your account". That is not an admin toggle; the first visit creates the environment.
4. Choose the routing mode
In the Claude App Home in Slack, pick Code only (every @Claude mention opens a Claude Code session) or Code + Chat (Claude routes between Code for engineering work and Chat for writing, analysis, or general questions). If Code + Chat answers as chat and you wanted code, use Retry as Code. If it picked the wrong repository, use Change Repo.
5. Invite Claude to the channel
The app is not added to channels automatically. In each channel where you want it:
/invite @Claude
It only responds to mentions in channels (public or private) where it was invited. It does not work in DMs.
The whole thread is the context
Mention @Claude in a thread and the entire thread goes in (or recent channel messages, if you mention it in the channel) so Claude can understand the problem and pick a repository. The official docs are explicit: Claude gets that context and may follow instructions from other messages in it. What that means in practice: anyone typing in the thread is talking to the agent that is about to touch your code. Use it in trusted conversations. Not in an open channel with people you do not control.
Once that holds, the bug thread is the best place to delegate from, because the context is already written. Add whatever is missing: files, errors, and what "done" means (tests, PR, docs).
When it finishes, Slack shows a summary and action buttons; the full transcript lives at claude.ai/code, where you can continue the session.
Plans and Claude Tag
On Pro and Max, this flow (a session under your individual account) is the documented path. On Team and Enterprise, Anthropic is retiring this version in favor of Claude Tag: @Claude as the organization's shared identity, with admin-configured access. The app and handle stay; what changes is who "Claude" is and how access is governed. If your workspace already migrated, follow the Claude Tag docs, not only this page.
Same axis, worth knowing before you delegate anything sensitive: on Team and Enterprise, sessions created from Slack are automatically visible to the organization.
Current limitations
- GitHub repositories only.
- One session, one PR.
- Claude Code on the web access is required; without it, Claude replies as normal chat.
- Usage counts against the plan of whoever starts the session (in this individual model).
Official docs: Claude Code in Slack
Requirements
- Pro, Max, Team, or Enterprise plan with Claude Code access
- Claude Code on the web enabled and at least one GitHub repo connected
- Claude app installed in the workspace and your account linked
@Claudeinvited to the channel where you mention it