Claude Code in Slack

Claude Code in Slack brings the power of Claude Code directly into your Slack workspace. When you mention @Claude with a coding task, Claude automatically detects the intent and creates a Claude Code cloud session, allowing you to delegate development work without leaving your team conversations. This integration is built on the existing Claude for Slack app but adds intelligent routing to Claude Code cloud sessions for coding-related requests. Each session runs under your own Claude account, using your connected repositories and your plan limits.

​

Use cases

• Bug investigation and fixes: Describe a bug and ask Claude to investigate and fix it.
• Quick code reviews and modifications: Have Claude implement small features or refactor code.
• Parallel task execution: Kick off coding tasks in Slack while you continue other work, receiving notifications when complete.

​

Prerequisites

Before using Claude Code in Slack, ensure you have the following:

​

Setting up Claude Code in Slack

​

How it works

​

Automatic detection

In Code + Chat routing mode, when you mention @Claude in a Slack channel or thread, Claude automatically detects whether your message is a coding task. Coding tasks go to a Claude Code cloud session. Anything else gets a regular chat reply. In Code only mode, every @mention goes to Claude Code. You can also explicitly tell Claude to handle a request as a coding task, even if it doesn’t automatically detect it.

​

Context gathering

• From threads: when you first @mention Claude in a thread, it gathers context from your messages and its own in that thread.
• From channels: when you @mention Claude directly in a channel, it looks at your recent messages and its own in that channel, and at the channel’s name, topic, and description.

This context helps Claude understand the problem, select the appropriate repository, and inform its approach to the task. To give Claude something a teammate wrote, such as an error report, paste its text into the message where you @mention Claude.

​

Session flow

1. Initiation: You @mention Claude with a coding request
2. Detection: Claude analyzes your message and detects coding intent
3. Session creation: A new Claude Code session is created on claude.ai/code
4. Progress updates: Claude posts status updates to your Slack thread as work progresses
5. Completion: When finished, Claude updates its message in the thread with its final response and action buttons, and sends you a direct message linking to it
6. Review: Click View session to see the full transcript, or Create PR to open a pull request

​

User interface elements

​

Message actions

• View session: Opens the full Claude Code session in your browser where you can see all work performed, continue the session, or make additional requests.
• Create PR: Opens GitHub’s compare page for the session’s branch, where you create the pull request. It appears on the status message Claude posted when the session started, once the session finishes.
• Switch to code repo…: If Claude responds in Chat but you wanted a coding session, click this button and select a repository, and Claude starts a Claude Code session with your original request.

​

Repository selection

Claude automatically selects a repository based on context from your Slack conversation. If Claude can’t tell which repository you mean, it asks you to choose: click Select repository and select one from the list.

​

Access and permissions

​

User-level access

​

Workspace-level access

Slack workspace administrators control whether the Claude app is available in their workspace:

​

Channel-based access control

Installing the app doesn’t add Claude to any channels. Claude responds to @mentions only in channels where it has been added; invite it with /invite @Claude. It works in both public and private channels. Admins can control who uses Claude Code by managing which channels Claude is invited to and who has access to those channels. This adds a layer of access control beyond workspace-level permissions.

​

What’s accessible where

In Slack: You’ll see status updates, completion summaries, and action buttons. The full transcript is preserved and always accessible. At claude.ai/code: The complete Claude Code session with full conversation history, all code changes, and file operations. Sessions stay in your Claude Code history at claude.ai/code, where you can continue past sessions, reference them, or create pull requests. For Enterprise and Team accounts, sessions created from Claude in Slack are automatically visible to the organization. See cloud session sharing for more details.

​

Best practices

​

Writing effective requests

• Be specific: Include file names, function names, or error messages when relevant.
• Provide context: Mention the repository or project.
• Define success: Explain what “done” looks like. Should Claude write tests? Update documentation? Create a PR?

​

When to use Slack vs. web

Use Slack when: You want to start a task asynchronously, or you’re collaborating with teammates who need visibility. Use the web directly when: You need to upload files, want real-time interaction during development, or are working on longer, more complex tasks.

​

Troubleshooting

​

“This workspace isn’t set up for Claude Tag yet”

@Claude replies in the thread with this notice instead of an answer when both of these are true:

• No organization has connected your Slack workspace to Claude Tag.
• The Claude account you linked in Slack isn’t on a Pro, Max, or Ultra plan.

Claude Tag is available on Team and Enterprise plans. To connect the workspace, start with the @Claude connect command the notice names, then follow Set up Claude Tag.

​

“The legacy Claude in Slack bot is retired”

The notice opens with The legacy Claude in Slack bot is retired effective October 5, 2026 and no longer responds in channels. Your Slack workspace is connected to a Claude organization. The earlier version is still selected for the channel, the workspace, or the organization default in that organization’s Claude Tag settings. The notice doesn’t depend on your own plan, so Pro, Max, and Ultra accounts get it too. If you’re an Owner of that organization, open Claude admin settings and turn on Claude Tag for the channel. To fix every channel that inherits the setting, change it on the workspace or the organization default instead. For the full move, see Migrate from the earlier Claude in Slack. If you’re not an Owner, send this entry to one.

​

”Claude Code is not enabled for your account”

This error means your Claude account has no cloud environment yet. Sign in at claude.ai/code once with the same account you connected to Slack and finish web onboarding, which creates your default cloud environment or asks you to create it. The error clears on your next mention. Each user must do this individually.

​

Sessions not starting

1. Verify your Claude account is connected in the Claude App Home
2. Check that cloud sessions are enabled for your account
3. Ensure you have at least one GitHub repository connected to Claude Code

​

Sessions from a Claude Tag channel fail to start

This entry applies to workspaces using Claude Tag. If you created the channel’s cloud environment at claude.ai/code, it belongs to your personal account, and Claude can’t start channel sessions in a personal environment. Claude Code fails the session immediately, and retrying doesn’t help. If you’re an Owner and the environment is your own, share it with the organization from the environment selector. Otherwise, an Owner recreates it as an organization-shared environment from the Cloud environments page in admin settings. You can apply it in two ways:

• Set it as the organization default at claude.ai/admin-settings/claude-code.
• Set it on the channel in the Claude Tag admin settings.

If you’re not an Owner, send this entry to one.

​

Repository not showing

1. Connect the repository at claude.ai/code
2. Verify your GitHub permissions for that repository
3. Try disconnecting and reconnecting your GitHub account

​

Wrong repository selected

Include the repository name in your request for more accurate selection.

​

Authentication errors

1. Disconnect and reconnect your Claude account in the App Home
2. Ensure you’re signed into the correct Claude account in your browser

​

Current limitations

• GitHub only: repositories must be on GitHub.
• One PR at a time: each session can create one pull request.
• Cloud session access required: users need access to cloud sessions.

​

Related resources