How to migrate from Claude in Slack to Claude Tag
The old Claude in Slack app is being switched off on August 3, 2026. You have a 30-day window to opt in on your own terms — or get migrated on Anthropic’s. Here is how to move deliberately, not by default.
What is changing and when
Claude Tag is the next generation of Claude in Slack, and the old app does not stick around. The facts that drive your timeline are simple.
- Claude Tag replaces the existing Claude in Slack app.
- Administrators have a 30-day window to opt in and migrate on their own schedule.
- On August 3, 2026, Claude in Slack is switched over to the new Claude Tag experience.
- Claude Tag is in beta for Claude Enterprise and Team customers and runs on Claude Opus 4.8.
The practical takeaway: you can either use the window to migrate deliberately, or let the cutover happen to you. The first path lets you decide the scope; the second hands you defaults.
A new app with a new posture
The old app was mostly a private assistant you queried. Claude Tag is a shared teammate that can work autonomously, remember channels, schedule its own tasks, and — if you enable it — act without being tagged. That is a meaningfully different security and behavior posture, which is why the migration deserves a decision rather than a click.
Decisions to make first
Settle these before you flip anything, ideally with whoever owns security and the Slack workspace.
- 01Confirm who holds Primary Owner or Owner in Slack — only they can configure Claude Tag.
- 02List the channels Claude should start in, and the channels it must stay out of.
- 03Decide the access scope per channel — which tools, data, and repositories each one needs, and nothing more.
- 04Decide where ambient mode is appropriate and where it stays off.
- 05Set token-spend limits for the organization and for the starting channels.
- 06Identify any regulated or residency-sensitive data and settle the compliance question before connecting it.
A sequence that de-risks the switch
Rather than enabling everything at once, stage the migration so you build confidence before you broaden it.
- 01Opt in within the 30-day window so you control the timing, not the August 3 default.
- 02Start in one or two low-risk channels with on-demand tagging and a tight tool scope.
- 03Keep ambient mode off until the on-demand workflow is reliable.
- 04Watch the audit view and the token-spend alerts through the first weeks of real use.
- 05Expand channel by channel, turning on ambient mode only where proactive work clearly helps.
- 06Document who owns the configuration, the review cadence, and the human approval gates.
The cutover is a chance to set it up right
A forced migration is rarely welcome, but this one is useful: it forces a deliberate decision about an AI teammate that most teams would otherwise switch on without thinking. The organizations that come out ahead are the ones that treat August 3 as a reason to scope, gate, and monitor properly from day one.
If you would rather not improvise that under a deadline, this is exactly the kind of cutover AIMOCS runs: mapping the channels, scoping access to least privilege, setting the approval gates and spend limits, and migrating in a staged sequence so the switch is controlled rather than chaotic.
When does Claude in Slack get replaced by Claude Tag?
Claude Tag replaces the existing Claude in Slack app. Administrators have a 30-day window to opt in and migrate on their own schedule, and on August 3, 2026, Claude in Slack is switched over to the new Claude Tag experience.
Is migrating to Claude Tag a simple swap?
No. The old app was largely a private assistant, while Claude Tag is a shared, autonomous teammate with channel memory, self-scheduled tasks, an ambient mode, and admin-controlled access. The migration is really a deployment decision about where it lives, what it can touch, and what it can do on its own.
Who needs to be involved in the migration?
A Slack Primary Owner or Owner must configure Claude Tag, since ordinary admins cannot. It is best to involve whoever owns security and the Slack workspace to decide channel scope, ambient-mode settings, token-spend limits, and any regulated-data questions before opting in.
What is a safe way to roll out Claude Tag?
Opt in within the 30-day window, start in one or two low-risk channels with on-demand tagging and tight tool scope, keep ambient mode off until the workflow is reliable, watch the audit view and spend alerts, then expand channel by channel. Put human approval gates in front of any consequential action.
What happens if I do nothing before August 3, 2026?
If you do not opt in during the 30-day window, Claude in Slack is switched over to the Claude Tag experience on August 3, 2026 with default settings. Opting in deliberately lets you control the scope, channels, and permissions instead of inheriting defaults.
We don't advise on AI. We run it for you.
Proven on your data before you commit.