Claude as a tag-able teammate in Slack — and what it teaches us about delegating to agents.
@Claude. It takes a request, breaks it into stages, and works through them with whatever tools an administrator has scoped to that channel — asynchronously, in full view of the channel, so anyone can steer it or pick up where the last person stopped. It remembers what happens in its channels so you stop re-explaining context, and (optionally) speaks up on its own when something needs attention. Anthropic frames it as "the beginning of an evolution of Claude Code" — the same agent, made proactive and multiplayer. It runs on Opus 4.8, in beta on Team and Enterprise plans.1,2
ClaudeTag is not a chatbot bolted onto Slack. It is the Claude Code agent, given three things it didn't have before: a persistent identity in your workspace, memory of the channels it lives in, and the ability to act without being prompted. Anthropic's framing is deliberate:
"the beginning of an evolution of Claude Code: it makes the model even more proactive, and it works better with a full team."1
You interact with it on three surfaces:2
@Claude in any channel hands it a task; it works in the thread where everyone can watch.The internal proof point Anthropic cites: 65% of their product team's code is now written by their internal version of ClaudeTag.1
When you tag it, ClaudeTag "break[s] its task down into stages and then work[s] through them in turn, using the tools it has access to."1 Two consequences matter:
@Claude task reads like a good subagent prompt: one clear objective, the stages implied or stated, and the tools it'll need already scoped in.
ClaudeTag "builds context by remembering relevant information from the channels it's in,"1,2 and with permission "can even automatically learn from other Slack channels and data sources."1 The point is to stop re-explaining context every session.
Two guardrails worth internalising:
With ambient behaviour enabled, ClaudeTag "will proactively keep you updated about whatever it thinks you might need to know … flag relevant information from across the channels it's in … and follow up on threads or tasks that have gone quiet without being resolved."1
prism-guardian and the medic fleet: poll state, compare against a baseline, raise the anomaly. Ambient ClaudeTag is a guardian you talk to. The lesson for prompt design: an agent that knows what "normal" looks like can be trusted to interrupt — define the baseline, or it'll either spam or stay silent.
Within a channel there is one ClaudeTag that everyone shares: "anyone can see what it's working on, and can pick up the conversation from where the last person left off."1 Admins can stand up separate Claude identities for different uses — a build-bot in one channel, a finance assistant in another — each with its own scope and memory.1
This is where ClaudeTag earns its place in an enterprise — and where the transferable craft lives. Administrators control three things:
| Lever | What it does |
|---|---|
| Access bundles | A named set of credentials, repository grants, plugins, and instructions that Claude uses on behalf of anyone in the channels it covers.3 |
| Channel scope | Elevated credentials (extra repos, sensitive data) can be confined to specific private channels. Memory stays scoped to the channels an admin defines.1,3 |
| Spend caps | Monthly channel cap from the org balance: $100 / $250 / $500 / $1,000 (default) / Unlimited / custom up to $1M. Work over the cap is declined entirely, not partially executed.2,3 |
| Audit log | Admins can "view a log of everything that @Claude has done."1 |
Access stacks at three levels: organization-wide credentials, workspace (all public channels), and private-channel grants for sensitive work. Only Primary Owners or Owners can configure it; on Enterprise, member access can be role-restricted.2
Four steps, Owner-only writes:3
@Claude connect for a 15-minute pairing code; choose whole-workspace or specific channels./invite @Claude then @Claude summarize this channel.| Claude Code | ClaudeTag | |
|---|---|---|
| Lives in | Your terminal / IDE | Your Slack workspace |
| Mode | You drive, turn by turn | You delegate; it works async |
| Audience | Mostly solo | Multiplayer — shared per channel |
| Initiative | Reactive | Proactive (ambient mode) |
| Memory | Session / files you give it | Persistent, channel-scoped |
| Best for | Deep hands-on work in a repo | Standing duties a team watches: triage, status, on-call, recurring ops |
They're the same lineage. Reach for Claude Code when you are in the loop on a hard change; reach for ClaudeTag when a standing duty should run where the team can see it.
Primary source to read first: Introducing Claude Tag — Anthropic Newsroom. It's short and it's canonical.
Community for wisdom: r/ClaudeAI for real-world setups as they emerge, and the Anthropic Discord for beta-specific scoping questions.