Claude Code in Slack: Setup, How It Works, and When to Use It

Claude Code in Slack lets you hand a coding task to Claude from a Slack channel. You mention @Claude with the task, Claude reads the thread for context, picks the repository, and starts a Claude Code cloud session under your own Claude account. It posts updates in the thread while it works, then mentions you with a summary and two buttons: View Session to see the full transcript, and Create PR to open a pull request. You never leave the conversation where the bug was reported.

It is built for one specific moment: a teammate drops a bug or a small request in Slack, and you want work to start right there, with the context everyone already wrote. It is not a replacement for sitting down in the Claude Code desktop app and building something step by step.

There are now two ways @Claude shows up in Slack, and which one you get depends on your plan. Check this first, because it decides which setup steps apply to you.

If you are a solo builder or freelancer on Pro or Max, Claude Code in Slack is your path, and the rest of this post is for you. It only answers in a workspace that no organization has connected to Claude Tag. If @Claude replies with a notice about Claude Tag instead of doing the work, that is the reason, and the fix belongs to whoever owns the Claude organization.

Mention @Claude in a thread and it reads every message in that thread. Mention it at the top level of a channel and it looks at recent channel messages. That context is how it figures out the problem and which repository to work in. If more than one repo could fit, it may show a dropdown, and you can always click Change Repo if it picked wrong.

Claude then creates a session on claude.ai/code, posts progress in the thread, and mentions you when it is done. From there you can open the session to read everything it did, keep going with follow-up requests, or click Create PR. Every session also stays in your Claude Code history, so nothing is lost when the thread scrolls away.

In Code + Chat mode, if Claude answers a coding request like a chat question, click Retry as Code to turn it into a coding session. It works the other way too.

My take: use Slack for small, well-described tasks where the context already exists in a thread. A bug report with the error message, a teammate asking for a copy change, a quick fix someone spotted in review. Write what done looks like, name the file or function if you know it, and say whether you want tests or a pull request. Then get on with your day and review the PR when it lands.

Use the desktop app for anything bigger or fuzzier: a new feature, a redesign, work where you want to watch and steer as it happens, or anything where you need to upload files. Anthropic's own guidance draws the same line. For checking work after it is done, Claude Code security review and GitHub Actions cover the review side, and Remote Control is the option when you want to continue a session from your phone instead of Slack.

If what you actually want is a bot your team or a client owns, with its own commands and behavior, that is a different thing. How to build a Slack bot with Claude Code walks through building one.