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.

If your team already used the “Claude in Slack” app, Claude Tag is not an add-on — it’s the replacement. Anthropic has said Claude Tag replaces the existing Claude in Slack app, administrators have a 30-day window to opt in, and the legacy app is retired on August 3. So this isn’t a “should we try it” decision. It’s a migration with a clock on it. Here’s what actually changed, and what to check before you flip the switch.

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 4.8 underneath. Claude Tag runs 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 is available today in beta for Claude Enterprise and Team customers.

2. Administrators have 30 days to opt in and migrate.

3. The old Claude in Slack app is retired on August 3. If you do nothing, that capability goes away.

Anthropic is also issuing an introductory launch credit to eligible Enterprise and Team organizations, which makes the trial period genuinely 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 covers 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, and the clock makes the decision for you anyway. For client delivery, migrate 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.