Claude Tag vs. the Old Claude in Slack App: What Changed

This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

Last refreshed: October 20, 2026 (Pacific)

If your team already used the “Claude in Slack” app, Claude Tag is not an add-on — it’s the replacement. Anthropic replaced the Claude in Slack app with Claude Tag, gave administrators a 30-day window to opt in, and retired the legacy app on August 3, 2026. The migration window has closed — here’s what actually changed, and how to run the new setup right.

What’s genuinely new

The old integration was, in practice, a way to summon Claude in a thread. Claude Tag changes the model from “a chatbot you call” to “a teammate that stays.” Four things are new:

• Multiplayer per channel. Within a given Slack channel, there’s one Claude that interacts with everyone. Anyone can tag it in and pick up where the last person left off, instead of each person holding a private session.
• Ambient mode. When enabled, Claude proactively keeps people updated about what it thinks they need to know — flagging relevant information, following up on forgotten threads — rather than waiting to be asked.
• Cross-channel learning. With permission, Claude can learn from other Slack channels and data sources. (Anthropic notes it doesn’t report from private channels.)
• Opus 5.5 underneath. Claude Tag now runs on Opus 5.5 (it launched on Opus 4.8), so the reasoning behind the delegation is the current-generation model, not whatever the old app was pinned to.

The migration timeline, plainly

Three dates and facts matter:

1. Claude Tag shipped (beta) for Claude Enterprise and Team customers.
2. Administrators had 30 days to opt in and migrate — that window is now closed.
3. The old Claude in Slack app was retired on August 3, 2026 — teams that never migrated lost that capability.

Anthropic also offered an introductory launch credit to eligible Enterprise and Team organizations; it has since expired, but it made the trial period low-stakes for internal use.

What to check before you switch — especially if you serve clients

For a single-company team, migrating is close to a no-brainer: you get a better model and a more capable teammate, and the launch credit covered the experiment. If you’re an agency or anyone handling more than one client’s data in one workspace, three checks come first:

1. Decide cross-channel learning per channel, not globally. The new superpower is also the new risk. A channel that holds one client’s data should never feed learning that another client’s work can draw on. Map your channels to trust boundaries before you grant any cross-channel permission.
2. Default ambient mode OFF for client-facing channels. Proactive surfacing is wonderful internally and dangerous across tenants. Turn it on where the data is all yours; leave it off where it isn’t.
3. Keep your approval gate. Whatever human sign-off you had on outbound work in the old setup, carry it forward. A more autonomous teammate raises the stakes on “who hits send.”

Our take

Adopt it internally now — the model upgrade and the multiplayer surface are worth it, . For client delivery, switch deliberately: the same features that make Claude Tag better make isolation harder, and isolation is the thing you can’t get wrong. We unpack exactly that failure mode in The Multi-Client Isolation Trap, and the on/off call for proactive behavior in Claude Tag Ambient Mode.

For the full picture, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.