On Tuesday afternoon, Anthropic stopped pretending Claude was a chatbot.

On June 23, 2026, at 5:00 PM UTC, Anthropic launched Claude Tag, a persistent, channel-resident AI teammate that lives inside Slack workspaces for every Claude Team and Enterprise customer in beta (The Verge, Anthropic).

Tag @Claude in a thread. Hand it a task. Walk away.

When you come back, the work is done in the thread, the channel context is intact, and your teammate who jumps in two days later picks up exactly where you left off because there is one shared Claude identity per channel, not 11 private ones in 11 private DMs (Lushbinary).

That sentence is the entire business story of the week.

Because the moment one AI vendor figures out how to put a shared coworker inside the place your team already lives, every founder reading their inbox has to decide which channels deserve that coworker and which ones never do.

You have a 30-day opt-in window before Anthropic phases out the old Claude in Slack app on August 3, 2026 (Lushbinary, Basic Tutorials).

If you have not written a charter for that decision yet, this post is your charter.

What Did Anthropic Actually Ship Inside Slack On June 23, 2026?

Five real changes, all on the same day.

First, Claude Tag itself. A new product that turns Claude into a permanent participant inside a Slack channel rather than a one-to-one DM. Tag @Claude. Get work back in a thread (Anthropic).

Second, shared channel memory. One Claude identity per channel. Everyone in the channel sees what Claude has been told, what tasks are in flight, and what it has learned. New teammates who join the channel walk into a coworker who already knows the context (ZDNET).

Third, ambient mode. Claude Tag can monitor a channel proactively without being prompted, flag relevant updates, follow up on forgotten threads, and surface what matters across an organization. Cat Wu, Anthropic's head of product for Claude Code and Cowork, framed it as "always on" (The Star).

Fourth, agentic action. Claude Tag can compose and merge pull requests, retrieve sales data, run analyses, manage assigned tasks, and break complex work into stages that run asynchronously for hours before reporting back in-thread (The Verge, IT Brief UK).

Fifth, admin scoping. Administrators choose which channels Claude can join, which tools and data sources it can touch, and what monthly spending limit applies per channel (IT Brief UK).

It runs on Opus 4.8. Cat Wu told Bloomberg the original plan was to anchor Claude Tag on the now-restricted Fable 5 model, with Opus 4.8 as the production backbone (The Star).

The eyebrow-raiser. Anthropic says 65 percent of its own product team's code is already written by the internal version of this product (YouTube · AI Daily).

That is not a forward-looking promise.

That is the team that shipped this telling you what they ship code with.

Why Does Claude Tag Reshape The Workflow For Slack-Native Businesses?

Because the unit of AI inside your company just changed from "an assistant" to "a coworker."

Until June 23, your team's AI usage looked like this. Each employee opens their own ChatGPT or Claude tab. They paste their own context. They do their own work. None of the answers, the prompts, or the memory are shared. When the employee leaves, the institutional knowledge they accumulated in their private chats walks out with them.

Starting June 23, your team can share a Claude. In #sales. In #engineering. In #customer-success. In #ceo-thoughts if you are brave.

Every conversation in that channel becomes shared institutional memory. Every Loom that someone drops becomes context Claude can use to brief the next teammate. Every customer issue resolved in #support becomes training data for the next ticket.

That is not a productivity feature.

That is a different kind of company.

This is also a direct shot at Microsoft Copilot in Teams. Anthropic chose Slack first because Slack-native businesses are the early-adopter wedge for agentic AI, and Slack itself has been quietly opening its surface to richer agent integrations (ZDNET).

If you run a SaaS, an agency, a coaching business, an e-commerce brand, or a services firm that already lives in Slack, you are the first wave.

What Is The Channel Charter Doctrine?

The Channel Charter Doctrine is a five-question template that any owner can write up in 30 minutes and use to govern Claude Tag, or any resident AI teammate, across their Slack workspace before the August 3 phase-out.

It is not security theater. It is the document that decides where a permanent AI coworker can and cannot listen, act, and remember.

Question 1: Which Channels Get A Resident Claude, And Which Never?

Not every channel deserves a coworker that remembers.

engineering, #support, #revenue-ops, #marketing-ideas. Yes. These are channels where shared memory is a strength.

legal-strategy, #board-prep, #hiring-feedback, #compensation, #cofounder-DM. No. These are channels where shared AI memory becomes a discovery liability if you are ever audited, sued, or acquired.

If your charter does not name both sides of that line, you do not have a charter.

Question 2: What Tools And Data Sources Does Claude Connect To In Each Channel?

Claude Tag's power comes from the tools an admin connects to each channel. Slack alone is a coworker who can read. Connect Linear, GitHub, Notion, Salesforce, Stripe, or your CRM, and you suddenly have a coworker who can act (Basic Tutorials).

Write a one-line connection map per channel. #support gets Zendesk and your KB. #engineering gets GitHub and Linear. #revenue gets Stripe and HubSpot.

The default should never be "all of them."

Question 3: Who Is Your Single Claude Tag Owner?

One named person.

This is not the IT lead. This is not the founder. This is the person who is on the hook when ambient mode posts a comment that lands wrong in front of a client, when a channel exceeds its spending cap, or when an audit asks who can access which channel.

If nobody owns it, everybody owns it, which means nobody owns it.

Question 4: What Is The Monthly Spending Cap Per Channel?

Anthropic lets administrators set monthly spending limits per Claude identity (Basic Tutorials).

Use it.

A 5-person engineering channel that lets Claude run autonomous code review can burn $2,000 in a week without intent. A $300 monthly cap on a non-critical channel is the cheapest insurance policy you will write in 2026.

Question 5: Have You Migrated Off The Old Claude In Slack App?

Anthropic gives administrators a 30-day opt-in window to switch from the legacy Claude in Slack app to Claude Tag. The legacy app is being retired on August 3, 2026 (Lushbinary).

If you do not opt in, you lose the old Claude integration and do not gain the new one.

Put the migration on the calendar this week. Not next month.

That is The Channel Charter Doctrine.

Five questions. One page. Posted in #leadership before Friday.

Why Did Anthropic Reserve Claude Tag For Team And Enterprise Plans Only?

Because the product depends on access without becoming a "free-roaming internal observer" (YouTube · AI Daily).

Solo Claude Pro accounts do not have admin scoping, channel-level permissions, or per-channel spending caps. Without those guardrails, a resident AI in a Slack channel is a leak waiting to happen.

By restricting beta to Claude Team and Enterprise, Anthropic forces the product into organizations that already have formal oversight of access, usage, and budgets (IT Brief UK).

For solo founders or sub-five-person teams without Enterprise plans, this means two things.

First, push to upgrade to Claude Team if Slack is your operational backbone. The price-to-capability ratio for a 3-to-10-person team adding a shared Claude coworker is one of the better deals in 2026.

Second, if your business is still in a Discord, WhatsApp, or iMessage operating mode, Claude Tag is your forcing function to consolidate communication into a single workspace where a resident AI teammate can actually create compounding institutional memory.

How Should A 12-Person Business Actually Use This This Week?

Three actions. None of them require an enterprise license.

First, write the charter. Five questions above, one page, posted to your #leadership channel by Friday. Pre-decide which channels get a Claude Tag identity and which never.

Second, name the owner. One person. Not a committee. They get to say yes or no to new channel deployments and they own the monthly spending caps.

Third, run a single channel pilot for two weeks. Pick a high-volume, low-risk channel like #support, #sales-questions, or #ops-ops. Connect one tool. Set a $300 monthly cap. Watch how often Claude saves your team 30 minutes versus how often it adds noise.

Two weeks from today, your team will either know exactly where Claude Tag belongs across the workspace, or you will know it does not fit your business at all.

Either outcome is worth more than ignoring the August 3 deadline.

If you want a guided rollout where we write the charter for your business, deploy the first three channels, and integrate it with your existing tool stack, the fastest path is to book an AI Implementation Session and we can walk you through it.

Frequently Asked Questions About Claude Tag In Slack

Is Claude Tag the same product as Claude in the regular Slack app?

No. Anthropic explicitly states that Claude Tag replaces the previous Claude in Slack integration. Administrators have a 30-day window to opt in to the migration, and the old app is being phased out on August 3, 2026 (Basic Tutorials). The old app was a one-to-one chatbot you could DM. The new product is a shared, channel-resident AI teammate with persistent memory, agentic capabilities, and admin-scoped access.

What model does Claude Tag run on?

Opus 4.8 today. Anthropic told Bloomberg that Fable 5 was the originally planned underpinning, but Fable 5 was restricted earlier in 2026, so Claude Tag launched on Opus 4.8 (The Star).

Is Claude Tag available outside of Slack?

Not yet. Anthropic launched Slack as the first surface and said it plans to bring Claude Tag to additional platforms over the coming weeks. Cat Wu, head of product for Claude Code and Cowork at Anthropic, confirmed expansion is planned (The Star). For now, if your team is on Microsoft Teams or Discord, you are waiting.

How much does Claude Tag cost?

Claude Tag is available in beta to Claude Team and Enterprise plan customers, and Anthropic is providing an introductory launch credit to qualifying Enterprise and Team organizations (ZDNET). Per-channel usage is billed against the team's Anthropic spend, with administrators able to set monthly spending caps per Claude identity.

What is the biggest privacy risk with Claude Tag?

Shared channel memory. One Claude identity per channel means every teammate who joins the channel inherits the AI's accumulated context, which can include past tasks, retrieved data, and tool actions. The mitigation is admin scoping, which is why The Channel Charter Doctrine question one is the most important: which channels get a resident Claude, and which never. If a channel contains compensation conversations, legal strategy, or M&A prep, the answer should usually be never.

TL;DR For Busy Owners

• Anthropic launched Claude Tag on June 23, 2026, at 5:00 PM UTC, a persistent AI teammate that lives inside Slack channels for Claude Team and Enterprise customers in beta (The Verge, Anthropic).
• One shared Claude identity per channel with persistent memory, ambient monitoring, agentic actions (PRs, sales data retrieval, task management), and admin-scoped tools, data, and spending caps (IT Brief UK).
• Runs on Opus 4.8. Anthropic says 65 percent of its internal product team's code is already written by the internal version of this tool (YouTube · AI Daily).
• Replaces the legacy Claude in Slack app. 30-day admin opt-in window, with the old app phased out on August 3, 2026 (Lushbinary).
• The doctrine for owners: The Channel Charter Doctrine. Five questions. Which channels get a resident Claude. What tools each channel connects to. Who owns Claude Tag in your org. What is the monthly cap per channel. Have you migrated off the old app yet.
• Action this week: write the charter, name the owner, run a single-channel pilot. Book your AI Implementation Session if you want a guided rollout.