The most surprising thing Anthropic said at launch
Anthropicclaims 65% of its own product team's code is now generated by an internal version of Claude Tag. That is a striking assertion — and it is doing real work in the product narrative. It positions Claude Tag not as a productivity add-on but as infrastructure Anthropic itself depends on. Treat it as a marketing claim until there is independent corroboration, but do not ignore it either: if even roughly accurate, it signals something meaningful about how Anthropic's own engineering culture has shifted.
What Claude Tag actually does
Claude Tag replaces Anthropic's existing Claude in Slack app. It is available today in beta for Enterprise and Team customers.
The core mechanic is simple: an administrator connects Claude Tag to a Slack workspace, scopes it to specific channels, grants it access to tools and data sources, and sets token-spend limits. From there, any team member in those channels can type @Claude with a request — draft a pull request, pull sales data, run an analysis — and Claude will execute it, reporting back in a thread.
Four things differentiate it from prior integrations:
- **Multiplayer by design.** One Claude per channel, shared across all members. Anyone can see what it is working on and continue where someone else left off. - **Persistent memory.** Claude accumulates context as it follows channel activity. Users do not re-explain projects from scratch. With permission, it can also draw context from other channels and connected data sources — but Anthropic says it will not pull from private channels. - **Ambient monitoring.** With this mode enabled, Claude proactively surfaces information it judges relevant and follows up on threads that have gone quiet. This is not a chatbot responding to prompts; it is an agent making editorial decisions about what its teammates need to know. - **Asynchronous work.** Claude can pursue multi-step tasks over hours or days without human hand-holding.
The product runs on Claude Opus 4.8, released in late May. Anthropic reported benchmark improvements with that model: agentic coding scores rose from 64.3% to 69.2%, and a knowledge-work benchmark moved from 1,753 to 1,890. Those are real improvements on specific evals — they do not straightforwardly translate to real-world performance, and Anthropic has not published the full methodology.
The governance questions enterprises need to answer first
Three risks deserve serious attention before procurement teams sign off.
**Vendor lock-in is structural, not incidental.** A Claude that has spent six months absorbing a channel's institutional memory — project history, team dynamics, decision rationale — is not easily swapped out. This is not a bug in the product design; it is the point. Enterprise buyers who have spent years negotiating multi-cloud flexibility should think carefully about what it means to hand that leverage to a single AI vendor.
**Ambient monitoring is a new governance category.** Most enterprise AI policies were written for tools that respond to explicit requests. An agent that continuously monitors information flows and decides what to surface operates differently. Regulated industries in particular will need updated frameworks before enabling this mode.
**Pricing opacity matters for always-on agents.** Anthropic uses token-based billing with administrator-set spend limits. An agent that monitors channels continuously, builds memory, and works asynchronously will consume tokens very differently than a tool invoked on demand. Budget owners should model this carefully before broad rollout.
Why Slack became the battleground
Anthropicis not alone here. Salesforce announced more than 30 new Slackbot capabilities in March. OpenAI introduced Workspace Agents in April. Perplexity, Cognition's Devin, and Microsoft's GitHub Copilot in Teams are all competing for the same real estate.
The logic is straightforward: the AI system that lives where work is coordinated accumulates the context that makes it hardest to replace. The collaboration layer is not just a distribution channel — it is a data moat in formation.