Claude Mastery Free ~9 min · interactive What's new · June 2026

Claude Tag — the teammate you @mention.

In June 2026 Anthropic replaced its old "Claude in Slack" app with Claude Tag: a persistent @Claude that lives in a channel, remembers context, and can be handed work by anyone on the team. It's a real shift from "a chatbot I DM" to "a coworker the whole channel shares." Here's what it actually does, how it's different from what came before, and how to use it without it turning into noise.

01 The core idea: one Claude per channel

The old Slack app was basically you, privately, talking to Claude. Claude Tag is different in a way that matters: it's one shared Claude instance per channel, visible to and usable by everyone in it. You @mention @Claude, hand it a task, and go back to your own work while it runs. Anyone else in the channel can do the same, and they're all talking to the same teammate — not separate private copies.

Why "shared" changes things

Because it's one instance in a shared space, Claude can build context from the channel itself — remembering relevant information from the conversations it sits in, and planning tasks to do later. That's what turns it from a vending machine you query into something closer to a team member who already knows what you're working on.

02 What it can actually do

CapabilityWhat it means in practice
Delegation@mention Claude with a task and keep working; it handles it async and replies in-thread
Shared context & memoryRemembers relevant info from the channels it's in, so you don't re-explain every time
Tool & data connectionsCan connect to your tools, data, and codebases to actually do the work, not just chat
Proactive updates (optional)If ambient behavior is on, it flags things it thinks you'll need and follows up on stalled threads

That last one is the most double-edged, so it gets its own honest note.

"Proactive" can become "noisy." Ambient behavior — where Claude jumps in with updates and chases unresolved threads on its own — is genuinely useful in a focused channel, and genuinely annoying in a busy one. Treat it as a dial, not a default. Turn it on in a channel with a clear job; leave it off where people are just talking.

03 How it's different from the old Slack app

Old "Claude in Slack"Claude Tag
ShapeA bot you mostly DM, one-to-oneA shared teammate in the channel
MemoryLargely per-conversationBuilds context from the channels it's in
Working styleAnswers when askedDelegated tasks, async work, optional proactive follow-ups
Who it servesYouEveryone in the channel

If your org already used the old app, note the migration: Claude Tag replaces it, and administrators have 30 days to opt in. It's available in beta for Claude Enterprise and Team customers — so it's a workspace-admin decision, not something an individual flips on alone.

Quick check

What's the single biggest change from the old Slack app to Claude Tag?

04 The honest read

Anthropic isn't shy that this is how they work now — they say tagging @Claude is one of the main ways the company gets things done, and that a large share of one product team's code is written by their internal version of it. Take the specific number with a grain of salt (it's a vendor's self-report), but the direction is real: chat-style AI is moving toward delegation — you hand off a task and check the result — rather than turn-by-turn Q&A.

The skill that matters is the same one good managers have: writing a clear hand-off. A vague @mention gets a vague result. "@Claude summarize this thread into three decisions and owners, and post it here by EOD" gets something useful.

05 Where should you actually use it?

Pick your channel
How to set it up

Your move

Pick one channel with a recurring chore — a standup summary, a triage queue, a weekly digest — and write the hand-off you'd give a new teammate to own it. That exact wording is your first @Claude task. If you can't write a clear hand-off, that's worth knowing too: the task may be fuzzier than you thought.

More Claude lessons →

What you can do now

  • Understand the shift: Claude Tag is one shared @Claude per channel, not a private DM bot
  • Delegate like a manager — write clear, specific hand-offs with the output and deadline you want
  • Treat proactive/ambient updates as a dial: on in focused channels, off in noisy ones
  • Remember it's beta for Enterprise and Team; an admin opts in (30 days to migrate from the old app)
  • Don't over-trust vendor stats — judge it on the work it returns in your channels
More in Claude Mastery

Projects, Artifacts, and the rest of the Claude toolkit

Where Claude Tag fits alongside Projects, MCP connections, and Claude Code in real team workflows. Browse the Claude track →

🎓
AI Coach
Ask anything about this lesson
Hi! I'm your AI Coach for this lesson on Claude Tag. Want help writing a clean @Claude hand-off, or deciding which channel to try it in first? Tell me what your team's channel is for.
Free lesson coaching is limited to 3 questions. Upgrade to Pro for unlimited coaching on every lesson.