What do existing Claude for Slack users need to do?

You must manually migrate to Claude Tag before July 23, 2026. The old app retires August 3. Permissions do not transfer automatically. Your Slack Workspace Owner needs to re-configure all tool connections and channel authorizations from scratch.

What is Ambient Mode and what are the risks?

Ambient Mode lets Claude Tag monitor authorized channels and take action without being @mentioned. It's off by default and must be enabled per channel. The key risk: there's no built-in human approval step. For regulated industries (finance, healthcare, legal), this could create compliance exposure.

How does Claude Tag billing work? Can costs spiral?

Channel work is billed at API usage rates to the organization account. DMs are billed to the individual's claude.ai account. There's no per-seat pricing. Spend alerts fire at 75% and 95% of your cap, and tasks are blocked (not truncated) when the cap is hit, so costs can't quietly spiral.

What is the minimum team size for Claude Tag?

Team plan requires at least 10 paid seats to enable Claude Tag, and qualifies for a $2,500 launch credit valid until September 1, 2026. Enterprise plans receive $25,000 in launch credits.

How does Claude Tag handle data privacy?

Claude Tag only accesses explicitly authorized channels. It cannot read your entire workspace. Data is deleted within 30 days of disconnection. Private channels and DMs require individual authorization, giving organizations fine-grained control.

Claude Tag: Slack Just Got a Virtual Employee. What You Need to Know Before Aug 3

Most people see Claude Tag and think: another AI chatbot integration. That framing misses what's actually changed.

Claude Tag isn't an upgrade to your Slack AI bot. It's Anthropic's attempt to redefine what AI means inside an organization: shifting Claude from a tool you occasionally query into a virtual employee that actually works in your Slack workspace. It maintains organizational memory across sessions, can execute tasks asynchronously, and with Ambient Mode enabled, can act on channel activity without being @mentioned.

This shift brings genuine capability gains, but also new governance gaps and a completely different billing model. There's also a hard deadline: the legacy Claude for Slack app retires on August 3, 2026, with the migration window closing July 23.

TL;DR

Hard deadline: Legacy Claude for Slack retires August 3, 2026; migration window closes July 23
Identity shift: From personal user bot to org-level agent with persistent channel memory
Billing changes: No longer per-seat; API usage billed to org (channels) or individual (DMs)
Ambient Mode is powerful but ungoverned: No built-in human approval step. Evaluate carefully for regulated industries
Team plan minimum: 10 paid seats required to activate Claude Tag

The Core Problem with the Old Claude for Slack

If you used the previous Claude for Slack app, you experienced its biggest limitation firsthand: no memory between sessions.

Every new conversation started fresh. Claude didn't know your company's naming conventions, your ongoing projects, your team's preferences, or decisions made in previous threads. You had to re-explain context every time, the equivalent of onboarding a new contractor every single day.

The underlying architectural issue was identity. The old app was built on personal user credentials. Each person connected their own Claude account, and each conversation was a clean slate. This made it function like a personal AI assistant bolted onto Slack, not a shared organizational resource.

The problem wasn't that Claude wasn't smart enough. The problem was the identity and memory architecture. Claude Tag rebuilds from that foundation.

What is Claude Tag? How Does It Differ?

Claude Tag entered beta on June 23, 2026, available to Enterprise and Team plan subscribers. The core change: Claude moves from "personal tool" to "organizational agent."

Dimension	Legacy Claude for Slack	Claude Tag
Identity	Personal user credentials	Org-level agent identity
Memory	Session-based, resets each time	Persistent channel memory
Billing	Per-user / per-seat	Org-metered API usage
Work mode	Reactive only	Async + Ambient (proactive option)
Model	Per-account settings	Claude Opus 4.8
Retirement	August 3, 2026	Current beta

The organizational memory is the most significant change. For anyone who has worked with the Claude API directly, this is the difference between stuffing company context into every system prompt versus Claude actually living in your workspace and naturally accumulating institutional knowledge.

Andrej Karpathy framed it this way: "a new paradigm for interacting with Claude... significantly more inline with all other human activity org-wide."

Anthropic reported that 65% of their own product team's code is now written by Claude Tag, a data point that signals the depth of internal adoption before the product even launched publicly.

This follows a broader enterprise AI trend. Microsoft 365's Copilot agents operate on similar principles. For a comparison, see Microsoft 365 Agent Practical Guide.

Setup: 4 Steps, One Common Mistake

Here's the mistake most teams will make: they'll assign their Slack Admin to handle Claude Tag setup, and hit a wall. Claude Tag requires Workspace Owner permissions, not Admin.

In most organizations, Admins and Owners are different people. Workspace Owners are typically whoever created the workspace or was explicitly granted ownership. Figure this out before you start the setup process.

4-Step Setup:

Access admin settings: Sign in as Workspace Owner and go to claude.ai/admin-settings/claude-tag
Authorize your workspace: Connect your Slack workspace via Owner-level OAuth authorization
Select channels: Choose which channels Claude Tag can access. This is channel-level granular control
Configure tool connections: Choose which tools Claude Tag can use (search, code execution, etc.)

Critical: None of your existing tool connections or channel authorizations from the legacy app carry over. Everything requires reconfiguration, even if you had everything set up previously.

Anthropic recommends completing migration before July 23, 2026. Don't wait until the week of August 3. If anything goes wrong with your Workspace Owner access, you'll need time to resolve it.

Ambient Mode: Powerful Feature or Compliance Risk?

Ambient Mode is Claude Tag's most impressive capability, and also the most potentially problematic.

Common assumption: Ambient Mode makes Claude faster at responding. Reality: it changes Claude's fundamental nature from reactive to proactive.

What Ambient Mode does:

Claude monitors authorized channels without needing to be @mentioned
It automatically identifies tasks and executes them without waiting for explicit instructions
Completed work is reported back to the channel

Why this matters for compliance:

There is no built-in human approval step. This isn't a bug or oversight. It's a deliberate design choice that assumes you trust Claude to execute tasks autonomously.

For regulated industries (finance, healthcare, legal), this assumption may directly conflict with compliance requirements. Many regulations mandate human review of AI-generated decisions, particularly when those decisions involve customer data, financial operations, or patient information.

Questions worth answering before you enable Ambient Mode:

Does your industry have human review requirements for AI-assisted decisions?
Does your channel content include protected customer or employee data?
Has your legal team reviewed autonomous AI execution in business-critical workflows?

Ambient Mode is off by default and must be enabled per channel. Start with low-stakes internal technical channels to observe behavior patterns before expanding to business-critical conversations.

For deeper context on how Claude handles memory and information persistence, Claude Memory Feature Guide covers the underlying mechanics that make Ambient Mode possible.

How Does Billing Work? Will Costs Spiral?

Claude Tag's pricing model is easy to misunderstand, and the misunderstanding is expensive.

Common assumption: Claude Tag has a fixed monthly fee like a Slack integration. Reality: it's API usage billing, pay-as-you-go.

Billing structure:

Channel work: Billed at Claude Opus 4.8 API rates, charged to the organization's account
Personal DMs: Conversations with Claude Tag in DMs are billed to the individual's claude.ai account
Not per-seat: Regardless of how many Slack users you have, channel-side costs are based on actual API consumption

Spend protection:

At 75% of spend cap: alert notification sent
At 95% of spend cap: second alert
Above spend cap: tasks are blocked, not truncated

The "blocked not truncated" design is worth noting. Claude won't abandon a task midway through because of budget. The entire task is held until the budget is reset. This makes costs predictable but means workflows can suddenly stop at month-end if the cap is hit.

Launch credits (expires September 1, 2026):

Enterprise plans: $25,000 in launch credits
Team plans (10+ paid seats): $2,500 in launch credits

The credits expire September 1, making the next few months the lowest-cost window to evaluate the platform. If your organization is on the fence, these credits make a trial nearly free.

Is Claude Tag Right for Smaller Teams?

Claude Tag isn't just for large enterprises, but it has a meaningful threshold for smaller organizations.

Team plan requires a minimum of 10 paid seats to activate Claude Tag. For 5-8 person teams, this means either upgrading to a higher seat count or looking at alternatives.

By team size:

10+ seat Team plans: Claude Tag makes sense to evaluate. The $2,500 credit covers significant exploration time, and the setup investment is worthwhile at this scale.

Sub-10 teams: Direct Claude API integration with a custom workflow may offer more flexibility. Claude Managed Agents provides a DIY path that lets you define memory and workflow behavior outside of Slack's structure.

Regulated industries (any size): Evaluate Ambient Mode governance requirements before committing, regardless of scale. The business case math changes significantly if you need to build approval workflows on top of Claude Tag.

Context on the broader market: Ramp's AI Index reports Anthropic has surpassed OpenAI in enterprise adoption (34.4% vs 32.3%). Claude Tag is part of that momentum, but adoption data doesn't tell you whether it fits your specific workflow.

Migration Timeline and Action Checklist

The window is shorter than it looks. Here's where things stand:

Date	Event
June 23, 2026	Claude Tag beta opens
July 23, 2026	Migration window closes
August 3, 2026	Legacy Claude for Slack fully retired

From this article's publication date, you have roughly 25 days to the migration window closing.

5-Step Action Checklist:

Identify your Workspace Owner: Find who actually holds Owner permissions in your Slack. If it's not clear, check Slack's Admin settings under "Workspace owners."
Pre-decide channel authorization scope: List which channels you're comfortable granting Claude Tag access to before you sit down to configure. Don't make these decisions in the setup flow.
Compliance review (if applicable): If you're in a regulated industry, get sign-off on Ambient Mode criteria before enabling it. This conversation takes time, so start it now.
Set spend caps: Decide on a monthly API budget before activating. The launch credits give you room to experiment, but set a hard cap anyway.
Start migration at claude.ai/admin-settings/claude-tag: Follow the 4-step process. Budget an hour for a complete migration if you have complex tool connections to reconfigure.

Conclusion: The Real Question Isn't Whether to Use It

Claude Tag represents a genuine paradigm shift: AI moves from tool to team member inside your organization. This isn't marketing language. It's a deliberate architectural choice Anthropic made, and what Andrej Karpathy meant when he said it aligns "with all other human activity org-wide."

Paradigm shifts come with new responsibilities. Organizational memory means Claude accumulates your company's information. Ambient Mode means it can act when no one is watching. API billing means costs are proportional to use, which is good until it isn't managed carefully.

If you're currently on the legacy Claude for Slack, you have no choice: migrate before July 23. If you've never used it, the launch credits make the next few weeks the best time to run a controlled pilot.

The right mental model for evaluating Claude Tag: imagine hiring a new virtual employee. Which meetings would you let them attend? Which files would you give them access to? Which decisions would you let them make unsupervised? That framing will take you further than any feature checklist.