Anthropic Launches Claude Tag: A Multiplayer, Context-Aware AI Teammate That Lives in Slack
Claude Tag lets teams invite Claude into Slack channels as a persistent, shared AI collaborator that remembers context, works asynchronously, and can take initiative without being prompted. It's available today in beta for Claude Enterprise and Team customers, and already powers 65% of Anthropic's own product team's code.
Enterprise/Team admins: pair Claude Tag with Slack workspace, grant tool access, set a monthly token spend limit, and test in a private channel before rollout.
Existing Claude in Slack users must opt in to migrate to Claude Tag within 30 days.
Tagging Claude is described as a multiplayer experience: one Claude instance serves an entire Slack channel, allowing any team member to see its work and continue where another left off.
Anthropic reports that usage has spread beyond engineering to product metrics, support tickets, and bug root-cause analysis internally.
Administrators can view a full log of everything Claude has done and who requested each task, providing an audit trail for governance.
65% of Anthropic's product team's code is currently created by their internal version of Claude Tag.
Claude Tag is available in beta starting today for Claude Enterprise and Team customers on Slack.
Claude Tag runs on Claude Opus 4.8.
Claude can schedule tasks for itself and pursue a project autonomously over hours or days.
Claude Tag replaces the existing Claude in Slack app; administrators have 30 days to opt in to migrate.
Claude Tag memories and tool access are scoped per channel, so a sales-configured Claude cannot share memories or data access with an engineering-configured Claude.
Claude does not report information from private Slack channels even when ambient behavior is enabled.
Claude Tag is framed as an evolution of Claude Code: more proactive, team-oriented, and collaborative rather than single-user or single-task.
'Ambient' mode: Claude proactively flags relevant information, follows up on quiet threads, and surfaces updates without being explicitly tagged.
Separate 'Claude identities' per channel: admins configure distinct tool access, data permissions, and memories for each channel context.
“We now spend much more of our time delegating tasks to many Claudes in parallel.”
Shared with Earmark · earmark-ai.com