Claude Code comes to Slack: tag @Claude in a thread and get back a pull request

Anthropic launched a Claude Code integration for Slack on December 8, 2025. The feature is in beta as a research preview, and the short version is this: you can now tag @Claude in a Slack thread, describe a bug or a feature request, and get back a completed pull request. No switching tools, no copying context across windows.

What it actually does

Previously, Claude in Slack was useful for lightweight things: writing a snippet, explaining an error, answering a quick question. Handy, but limited.

The new integration goes further. When you @mention Claude in a channel or thread with a coding-related request, it automatically detects that intent and spins up a full Claude Code session on the web, using the surrounding Slack conversation as context. It reads the thread or recent channel messages, works out what repository is relevant, does the work, then posts status updates back into Slack as it goes. When it’s done, you get a link to the full session and a direct link to open a pull request.

Anthropic points out something worth noting here: a lot of the critical context around engineering work already lives in Slack. Bug reports, user complaints, feature discussions, architectural debates. Before this integration, all of that context had to be manually moved somewhere else before a coding session could begin. Now it doesn’t.

Three things you can use it for right now

Anthropic has highlighted three primary use cases in the beta:

Bug investigation and fixes. When a bug report lands in Slack, you can tag Claude immediately, in the same thread. Claude reads the report, the surrounding discussion, any reproduction steps shared by the team, and gets to work.

Quick code reviews and modifications. If a teammate posts feedback asking for a refactor or a small feature addition, Claude can implement it directly from that thread without anyone needing to open an IDE.

Collaborative debugging. Sometimes the most useful debugging context comes from the conversation itself: a user describing unexpected behaviour, someone sharing a log, a back-and-forth about what changed last week. Claude can use all of that to inform how it approaches the problem.

How to get set up

You’ll need the Claude app installed in your Slack workspace via the Slack App Marketplace. Once installed, authenticate with your Claude account and you can start @mentioning Claude in channels.

A few things to know before you start:

• Claude Code in Slack works in channels only, both public and private. It does not work in direct messages.
• You need a Team or Enterprise Claude plan, and a Claude Owner or Primary Owner must enable Claude Code on the web via Organisation settings first.
• Individual users also need their own Claude Code on the web access enabled.
• There’s a routing mode called “Code + Chat” in the Claude App Home. If Claude routes something to Chat when you wanted a coding session, there’s a “Retry as Code” button to correct that.

What this means for your team’s workflow

The most practically useful aspect of this is the asynchronous angle. You can describe a task during a standup, Claude Code processes it in the background, and by the next morning there’s a PR ready to review. That’s useful for any team, and especially useful across timezones where handing off work between regions often means delays.

It also shifts where the work effectively begins. Several developers and commentators have noted that as coding agents become more capable, the starting point is moving away from the IDE and toward wherever the planning and coordination actually happen. For most teams, that’s Slack.

Rakuten reportedly reduced software development timelines from 24 days to 5 using Claude Code, a 79% reduction, which gives some indication of the productivity ceiling here when the tool is integrated into real workflows rather than used in isolation.

The security and access questions worth asking

Any integration that touches both your chat platform and your code repositories is worth scrutinising. A few things Anthropic has confirmed:

• Claude respects Slack’s existing permission structure. It cannot access conversations or repositories a user is not already authorised to see.
• By default, your Slack conversations are not used to train Anthropic’s models or stored within them.
• For Enterprise and Teams accounts, sessions created from Slack are automatically visible to the organisation, which helps with auditability.

The open question for security-conscious teams is operational risk: this adds a dependency on both Slack and Claude’s API being available and performing reliably. If either has an outage or hits rate limits at the wrong moment, workflows that depend on this integration will be disrupted. Worth factoring in before you build critical processes around it.

The bigger picture

Claude Code crossed $1 billion in revenue six months after its public debut. Customers include Netflix, Spotify, and Salesforce. The Slack integration, which reaches over 750,000 organisations on Slack’s platform, is a meaningful expansion of where Claude Code can be accessed and triggered.

For developers and engineering teams, the practical upshot is straightforward: the context you’re already creating in Slack can now directly drive coding work, without any manual translation step in between. That’s a genuine workflow improvement, and for teams already using both tools, it’s worth testing.