Anthropic Embeds @Claude Permanently in Slack on 23 June 2026
Anthropic launched Claude Tag in public beta on 23 June 2026, making it available to all Claude Enterprise and Team plan subscribers. Claude Tag replaces Anthropic's earlier Claude in Slack application, which gave each user a private AI assistant, with a fundamentally different model: a single shared @Claude in each Slack channel that the entire team can address, task, and redirect as a persistent member of that workspace. The product runs on Claude Opus 4.8. Teams have a 30-day window to migrate from the old per-user Claude in Slack app to Claude Tag, after which the older app is retired. Anthropic's own product team has been running an internal version of Claude Tag for several months, and the company reports that 65 per cent of the code produced by its product team is now generated by that internal version — including most of the code that built Claude Tag itself.
How Claude Tag Differs From the Old Claude in Slack App
The old Claude in Slack integration treated the AI as a private assistant that each individual user accessed separately, with no shared context between colleagues. Claude Tag operates as a single entity in a channel with persistent memory of the conversations and tasks it has participated in within that channel. A team member who tags @Claude to start a research task, another who adds context three hours later, and a third who asks for a status update the following morning are all interacting with the same AI instance that has followed the thread throughout.
This shift from per-user to per-channel architecture changes how teams use AI in their daily workflows. Rather than each engineer privately querying an AI and integrating results manually, the team can collectively delegate tasks to @Claude, receive updates in the shared channel thread, and have Claude's outputs visible to the full team without any additional coordination steps.
Ambient Mode: AI That Follows Up Without Being Asked
Claude Tag includes an optional ambient behaviour mode that teams can enable at the channel level. When ambient mode is active, Claude does not wait to be tagged. It monitors the conversations in its channel, identifies tasks that have been discussed but not completed, flags relevant information from other threads that bears on active discussions, and follows up on threads that have gone quiet. If a team agrees on a design decision in a Slack thread but nobody creates a ticket, an ambient Claude Tag instance may proactively surface that gap.
The ambient mode capability distinguishes Claude Tag from a traditional AI chatbot integration. Rather than answering questions when asked, an ambient Claude Tag instance functions more like a junior team member who reads everything in the channel and intervenes when it notices something actionable, without requiring explicit instruction on every occasion. Administrators can choose whether to enable ambient mode on a per-channel basis.
The 65 Per Cent Code Statistic
Anthropic's disclosure that 65 per cent of its product team's code is now generated by the internal version of Claude Tag is among the most specific enterprise AI productivity figures a major AI company has published. The figure is not a controlled study — it reflects Anthropic's own engineering culture, designed around maximal use of its own products, and the team's sophistication in workflow design and prompt engineering. Nonetheless, the number provides a concrete reference point for teams assessing what sustained AI-assisted engineering looks like in a professional setting.
For Indian software teams, the statistic is useful less as a prediction of their own output mix and more as a directional signal. Teams that have already integrated Claude, Cursor, or GitHub Copilot into individual coding workflows have observed productivity shifts that prior processes did not anticipate. Claude Tag applies similar logic to team-level Slack-native collaboration rather than individual IDE-level code generation, addressing the coordination layer that individual AI assistants do not directly solve.
What Admins and IT Teams Need to Know
Claude Tag gives administrators per-channel control over what tools and data Claude can access. A customer-facing support channel might be configured to give @Claude access to the support ticket system and knowledge base but not to internal engineering discussions. A product team channel might grant access to the product roadmap document store but not to billing data. Memory is isolated between channels by default, preventing @Claude in one team's workspace from accessing context from another.
This granular access model is significant for enterprise teams in regulated industries, including Indian banking, insurance, and healthcare organisations where data access controls are a compliance requirement. The ability to define what @Claude knows and what it can do at the channel level, rather than applying a single policy across the full Slack workspace, makes enterprise deployment in regulated contexts considerably more tractable.
What Claude Tag Means for Indian Engineering Teams
For Indian product and engineering teams, Claude Tag represents the next step after individual AI coding assistants. Most high-performing Indian engineering teams in 2026 have already adopted individual AI tools, and the productivity gains from individual assistance are well understood. The unresolved challenge is team-level AI coordination: how does a team collectively benefit from AI rather than running parallel private conversations with an AI and manually integrating the results?
Claude Tag's per-channel model directly addresses this. For a team of ten engineers working on a sprint, a shared @Claude in their Slack channel can track task allocation, surface blockers, generate and update specification documents, and follow up on open items across the sprint without requiring any individual team member to own that coordination overhead. The cost is an Enterprise or Team Anthropic subscription, a considerably smaller overhead than a dedicated coordination tool or engineering programme manager allocation.
The Bottom Line
Anthropic launched Claude Tag in public beta on 23 June 2026 for Enterprise and Team plan subscribers. Claude Tag replaces the per-user Claude in Slack app with a single persistent @Claude per channel that the whole team can task, redirect, and receive updates from, running on Claude Opus 4.8. An optional ambient mode lets @Claude proactively flag stalled tasks, surface relevant information, and follow up on quiet threads without being explicitly tagged. Admins control which tools and data @Claude can access per channel, with memory isolated between channels. Anthropic's internal version now generates 65 per cent of its product team's code. For Indian software teams, Claude Tag moves AI collaboration from the individual coding session into the shared team workspace, addressing the coordination overhead that individual AI assistants do not solve.
Frequently Asked Questions
What is Anthropic Claude Tag and how does it differ from the old Claude in Slack app?+
Claude Tag is Anthropic's new Slack integration, launched in public beta on 23 June 2026 for Enterprise and Team plan subscribers. It replaces the older Claude in Slack app, which gave each individual user a private AI assistant with no shared context between colleagues. Claude Tag places a single persistent @Claude in each Slack channel that the entire team can address, task, and redirect collectively. The shared instance builds context by following all conversations in its channel and can be assigned tasks that the team views and builds on together, rather than each member running separate private conversations with AI.
What does ambient mode do in Claude Tag?+
When ambient mode is enabled on a Claude Tag channel, @Claude does not wait to be tagged before acting. It monitors conversations in the channel, identifies tasks that have been discussed but not completed, flags information from other threads that may be relevant to active discussions, and proactively follows up on threads that have gone quiet. For example, if a team discusses a feature decision but no one creates an action item, an ambient Claude Tag instance may surface that gap unprompted. Administrators can choose whether to enable ambient mode on a per-channel basis, and it is off by default.
How does Claude Tag handle data privacy and admin controls?+
Claude Tag gives administrators per-channel control over what tools and data @Claude can access. A support channel might be configured with access to the ticketing system and knowledge base but not internal engineering discussions. A product channel might have access to the roadmap document store but not billing data. Memory is isolated between channels by default, so @Claude in one channel does not have visibility into conversations from another. This granular access model allows enterprise teams in regulated industries, including Indian banking, insurance, and healthcare organisations, to deploy Claude Tag in specific channels without granting it access to the full Slack workspace.
What does Claude Tag mean for Indian software engineering teams?+
Claude Tag moves AI collaboration from individual coding sessions into the shared team workspace, addressing a gap that individual AI coding assistants do not fill. For Indian engineering teams already using individual tools like Claude, Cursor, or GitHub Copilot, productivity gains from individual AI assistance are well established. Claude Tag extends this to the team coordination layer: a shared @Claude in a sprint channel can track task allocation, surface blockers, generate specification documents, and follow up on open items across the sprint without requiring any individual to own that overhead. This is particularly relevant for Indian product teams managing multiple simultaneous workstreams where coordination overhead often outweighs the cost of the tooling itself.
Written by
TechPillow Team
Sharing insights on technology, product development, and the Indian tech ecosystem.