Claude Tag is one of the most significant shifts in how AI works inside a business — and if your team uses Slack, this change affects you right now. Launched by Anthropic on June 23, 2026, Claude Tag transforms Claude from a private chatbot into a persistent, shared AI agent that lives directly inside your Slack channels. It is no longer just a tool you query in secret. It is now a virtual teammate that your whole team can delegate work to, at any time, without waiting for a reply from a human.
If you are currently using the old Claude for Slack app, you have a hard deadline: the legacy app retires on August 3, 2026. The migration window closes on July 23. This guide explains everything you need to know about Claude Tag — what it is, how it works, what makes it different, and how to set it up before it is too late.
What Is Claude Tag?
Claude Tag is Anthropic’s new enterprise AI agent for Slack. Instead of operating as a private DM bot that only one person can interact with at a time, Claude Tag operates as a channel-level agent — a shared, persistent identity that any member of an authorized Slack channel can interact with. Learn more on Anthropic’s website.
Think of it this way. With the old Claude for Slack, if you started a task with Claude, nobody else on your team could see what was happening, pick up where you left off, or build on the work. Claude Tag changes all of that. Once a system administrator provisions Claude Tag into a channel, the entire team can tag @Claude to delegate tasks, ask questions, run analysis, write code, review pull requests, or handle incident response — all within the same shared thread that everyone can see and continue.
Claude Tag runs on Anthropic’s Claude Opus 4.8 model, one of the most capable AI models available in 2026, purpose-built for complex, multi-step agentic tasks.
Key Features of Claude Tag
1. Shared Channel Identity
Claude Tag operates under its own system credentials inside Slack. It is not pretending to be a human, and it is not tied to any single user account. Any authorized team member in the channel can tag Claude, delegate a task, and any other team member can pick up that conversation and continue it. This makes Claude Tag genuinely collaborative in a way no previous AI Slack integration has been.
2. Persistent Memory Across Sessions
Unlike the old Claude for Slack, Claude Tag maintains organizational memory across sessions. It accumulates institutional context — project history, codebase details, team decisions — from the channels and tools it has been given access to. You do not have to re-explain the background every time you start a conversation.
3. Asynchronous Task Execution
This is one of the most powerful features. You can assign Claude Tag a complex, multi-step task and walk away. Claude will work on it autonomously over hours or even days, scheduling sub-tasks for itself and reporting back inside the thread when complete. No need to stay in the chat waiting for responses. This makes Claude Tag feel much closer to a real digital colleague than any previous AI tool.
4. Ambient Mode
Ambient Mode is an optional setting that allows Claude Tag to proactively monitor channels without being explicitly mentioned. When enabled, Claude can flag relevant updates, revisit inactive discussion threads, and follow up on unresolved tasks on its own initiative. This is the most autonomous feature of Claude Tag and requires careful administrator governance — especially in regulated industries where compliance review is required before enabling it.
5. Tool and Codebase Connections
Administrators can connect Claude Tag to external tools, databases, APIs, and even entire code repositories. This means Claude Tag can pull real data, execute code, push changes to repositories, and integrate with your existing workflows — not just chat about them. Common integrations include GitHub, Jira, internal databases, and custom APIs.
Claude Tag vs Old Claude for Slack: What Actually Changed
If you are wondering whether Claude Tag is just a minor update to the old Claude for Slack app, it is not. The architecture is fundamentally different.
- Old Claude for Slack: Individual DM-based, one user at a time, no shared context, no persistent memory, reactive only (only responds when prompted), no tool connections from Slack.
- Claude Tag: Channel-level agent, entire team shares the same Claude instance, persistent organizational memory, asynchronous multi-step execution, optional ambient proactive monitoring, full tool and codebase integrations.
The old app was a productivity shortcut. Claude Tag is infrastructure — it fundamentally changes how your team delegates and executes work. For more on AI-powered productivity tools, see our guide on Google AI Mode.
How to Set Up Claude Tag in Your Slack Workspace
Setting up Claude Tag requires Workspace Owner permissions — not just Admin. This is an important distinction. Here is the complete four-step setup process:
- Access admin settings: Sign in as Workspace Owner and go to
claude.ai/admin-settings/claude-tagto begin. - Authorize your workspace: Connect your Slack workspace via Owner-level OAuth authorization. This grants Claude Tag the permissions it needs to operate in your channels.
- Select channels and connect tools: Choose which specific Slack channels Claude Tag can access. This is granular, channel-level control. You also connect the external tools, data sources, and codebases Claude can use within those channels.
- Set monthly spend limits: Before going live, set a hard cap on your organization’s monthly token spend. Anthropic offers introductory launch credits for eligible Enterprise and Team customers — Team plans with 10+ paid seats receive $2,500 in launch credits.
Pro tip: Always test Claude Tag in a private channel first to confirm all tool connections and permissions are working correctly before rolling it out to your wider team channels.
Who Can Use Claude Tag?
Claude Tag is available in beta for Claude Enterprise and Team plan customers. It is not available on individual Pro or Max plans. Team plans require a minimum of 10 paid seats.
If you are on the legacy Claude for Slack app on any plan, you need to migrate before the July 23, 2026 migration window closes. Permissions from the old app do not transfer automatically — your Workspace Owner will need to re-configure all tool connections and channel authorizations from scratch.
The Migration Deadline You Cannot Miss
Here is the timeline you need to know:
- June 23, 2026: Claude Tag beta opens for Enterprise and Team customers.
- July 23, 2026: Migration window closes. After this date, you cannot opt in through the standard migration path.
- August 3, 2026: Legacy Claude for Slack app is fully retired. If you have not migrated, you lose access entirely.
Given that the current date is July 7, 2026, you have 16 days until the migration window closes. If your team depends on Claude in Slack for daily work, start this process today. Compliance reviews for Ambient Mode and internal security approvals can take time — do not leave this to the last week.
What Can Claude Tag Actually Do? Real Use Cases
Claude Tag is designed for teams that need to delegate complex, multi-step work that unfolds over time. Here are the most impactful real-world use cases:
- Software development: Tag @Claude in your engineering channel, ask it to review a pull request, write a unit test, or debug a specific function. Claude can access the codebase directly and post results back in the thread.
- Incident response: During a production incident, tag Claude to analyze logs, identify patterns, suggest fixes, and track the resolution thread — all in real time, with the entire on-call team watching.
- Data analysis: Connect Claude to your internal database and ask it to run analysis, generate reports, or compare datasets. Results come back into the channel where any team member can follow up.
- Product and project management: Ask Claude to summarize a week of channel activity, identify unresolved decisions, or draft a project update — pulling context from multiple channels if permitted.
- Support workflows: In a customer support Slack channel, Claude Tag can triage incoming issues, pull relevant documentation, draft initial responses, and flag escalations.
Is Claude Tag Worth It?
For teams already paying for Claude Enterprise or Team plans, Claude Tag is essentially free to activate (though usage still consumes tokens against your plan). The question is whether your team’s workflow benefits from a shared, asynchronous, channel-level AI agent rather than individual AI assistants.
If your team regularly collaborates on complex multi-step tasks, delegates work across time zones, or manages long-running projects in Slack — Claude Tag is a genuine upgrade. The persistent memory alone eliminates an enormous amount of context-setting friction that teams currently deal with every day.
If your team mostly uses Slack for quick Q&A and individual productivity, the old experience was sufficient. But given the August 3 retirement date, migration is no longer optional — you will need to move to Claude Tag regardless.
Final Thoughts
Claude Tag represents a fundamental shift in what AI means inside an organization. It is not a smarter chatbot. It is a persistent, shared, agentic team member that can work alongside your people, accumulate knowledge about your organization, and execute complex tasks autonomously over time. That is a different category of tool entirely.
With the legacy Claude for Slack app retiring on August 3, 2026, there is no reason to wait. If you are a Workspace Owner on a Claude Enterprise or Team plan, start the migration this week. Set up Claude Tag in a private channel, test your tool connections, configure your spend limits, and begin rolling it out to the channels where your team does its most complex collaborative work.
The teams that figure out how to work with AI agents effectively in 2026 will have a structural advantage that compounds over time. Claude Tag is one of the clearest opportunities to build that capability right now.