@Claude and Claude in Slack
Claude as a participant in team chat — mention it in Slack and it picks up the task, up to and including opening a pull request.
Last verified August 21, 2026 · 3 sources
@Claude is listed in Anthropic’s product navigation as its own entry, which tells you something:
Claude-in-chat is treated as a product surface, not a plug-in feature of something else.
What it does
In Slack, you mention Claude in a thread and it takes the work from there. The canonical documented example is routing a bug report to a pull request: someone describes a bug in a channel, mentions Claude, and a PR comes back.
Because the thread already contains the context — the report, the discussion, the links — this removes the step where a human re-explains the problem to a coding agent.
Where the boundary sits
There are two related things here and the docs keep them apart:
- Claude in Slack — the Claude Code integration, documented on the Claude Code docs site.
- Claude Tag — the broader tagging surface, also documented there.
Both are covered by the same source pages; this entry treats them together because the user-visible action is the same one.
What this page does not claim
Setup steps, workspace admin requirements and per-plan gating are documented upstream and are not reproduced here. Availability below Pro is recorded as unavailable based on Claude Code’s own plan gating, since the Slack route drives Claude Code.
Plan availability
Anything left blank is not documented publicly, not a claim that it is unavailable. Compare every feature at once in the availability matrix.
- FreeNot available
- ProIncluded
- MaxIncluded
- TeamIncluded
- EnterpriseIncluded
- APINot available
Sources
- 01Claude product overviewOfficialclaude.com@Claude appears in the product navigation as a distinct entry.
- 02Claude Code in SlackOfficialcode.claude.com
- 03Claude Tag — Claude Code docsOfficialcode.claude.com
Page changelog
- VerifiedConfirmed as a distinct product-nav entry and a documented Claude Code integration.