← Blog

Engineering note

Anthropic Introduces Claude Tag: Making Claude a Permanent AI Teammate for Your Team

Anthropic Introduces Claude Tag: Making Claude a Permanent AI Teammate for Your Team Industry Pulse Bloss0m Note 030

Summary

Anthropic officially launched the new team collaboration feature Claude Tag in June 2026. This marks Claude’s evolution from a single-user conversational AI to a “virtual teammate” that seamlessly integrates into team workflows. Teams can tag @Claude directly in Slack channels to assign tasks, authorize tool access, and let Claude autonomously plan and execute cross-system project work.

This article takes you deep into the core advantages of Claude Tag and summarizes its target audience, usage, and the billing model that enterprises care about most.

What is Claude Tag?

In the past, we were used to interacting with AI through one-on-one chat windows, but real work is often highly collaborative. Claude Tag is a brand new collaboration model: bringing Claude directly into Slack channels as a team member.

As long as Claude is granted permission to enter specific channels, access tools, databases, or even codebases, anyone in the channel can directly tag @Claude to assign tasks. It can remember the context of discussions within the channel, and autonomously plan and execute tasks, allowing human members to focus on other higher-value work.

According to Anthropic’s official disclosure, this feature is already the primary way of collaboration internally. Currently, up to 65% of the code produced by Anthropic’s product team is generated by an internal version of Claude Tag; this trend is also spreading to various scenarios such as customer support ticket processing, product data tracking, and root cause analysis of system bugs.

Core Advantages

Unlike the previous “Claude in Slack” bot, Claude Tag has been endowed with more powerful Agentic capabilities, featuring the following four characteristics:

  1. Multiplayer Experience (Multiplayer) In the same Slack channel, everyone faces the “same Claude with a shared memory.” Team members can see the tasks Claude is working on and even take over a previous colleague’s conversation with Claude at any time. This makes AI no longer an information silo, but a true center for team collaboration.
  2. Learns Over Time (Learns over time) As Claude continues to stay in the channel, it automatically builds an understanding of the project context. Users don’t need to explain background knowledge from scratch every time. With administrator authorization, Claude can even learn tacit knowledge from other Slack channels and data sources to deliver outputs more aligned with the company’s current situation.
  3. Takes Initiative (Takes initiative) If “Ambient behavior” is enabled, Claude will proactively provide updates for the team. It can integrate relevant information across channels and even proactively track discussion threads or tasks that have gone quiet and remain unresolved.
  4. Works Asynchronously (Works asynchronously) After assigning a task to Claude, you can turn around and handle other work immediately. Claude can schedule its own timeline, autonomously advance the project over the next few hours or days, and report back in the Slack thread upon completion or when encountering obstacles.

Target Audience and Applicability

Currently, Claude Tag focuses on serving enterprise and team customers, and is temporarily unavailable to individual plan users.

  • Supported Plans: Exclusive to customers of the Claude Team and Claude Enterprise plans.
  • Unsupported Plans: Not yet open to individual subscription plans such as Free, Pro, or Max.

For enterprise organizations that have already centralized a large amount of daily communication, operational discussions, code reviews, and support tickets on Slack, Claude Tag will deliver maximum value.

Usage and Setup Process

Claude Tag replaces the legacy Claude in Slack application. To ensure enterprise data security, Claude’s identity and access permissions can be strictly limited. For example: you can create Claudes with different permissions for the “Sales Team” and the “Engineering Team,” where the sales channel’s Claude cannot access the engineering codebase, and vice versa.

Implementation and Setup Steps

System administrators can configure it through the Claude Console (claude.ai/admin-settings/claude-tag) in the following four steps:

  1. Link Workspace: Bind the Claude Tag app to the company’s Slack Workspace.
  2. Authorize Tool Access: Grant Claude permissions to access internal APIs, databases, or other SaaS tools based on the needs of different channels or teams.
  3. Set Budget Limits: To avoid overspending, administrators must set an overall monthly Spend Limit for the organization.
  4. Sandbox Testing: Test Claude’s operation in private channels before rolling it out company-wide.

Once setup is complete, employees simply enter @Claude along with instructions in an authorized Slack channel to trigger automated workflows. If interacting with Claude via Direct Message (DM), the employee’s personal tool settings will be used by default.

Billing Model and Cost Control

Because Claude Tag has Agentic workflow capabilities (requiring repeated reasoning, calling tools, and reading long conversation histories), its token consumption is typically higher than traditional conversational Q&A. Therefore, Anthropic has adopted a more flexible billing mechanism:

  1. No Additional Subscription Fee, “Consumption-Based” Billing As long as you are a Team or Enterprise customer, you can enable the Claude Tag feature for free, with no extra “feature buyout fees” or “seat fees.” All costs are based entirely on the number of API tokens consumed when Claude actually executes tasks.
  2. Organization and Channel-Level Budget Control To prevent astronomical unexpected bills when AI executes autonomous tasks (like turning on Ambient Mode to actively listen to a channel), Anthropic mandates that administrators set monthly Spend Caps. Administrators can even set independent token consumption limits for individual channels.
  3. Billing Attribution
    • Public/Shared Channels: The costs incurred by teams tagging @Claude in Slack channels will be uniformly billed to the organization level.
    • Direct Messages (DMs): Interactions with Claude through DMs or the personal Assistant Panel are usually subject to the individual account’s quotas or separate API billing rules.
  4. Launch Credit To encourage enterprise customers to transition and test painlessly, Anthropic is offering an initial Launch Credit to eligible Enterprise and Team organizations, allowing the entire company to experience this new feature without worrying about the bill.

Conclusion

The launch of Claude Tag officially heralds the arrival of the “multi-agent and human collaboration” era. It is no longer just a tool that passively answers questions, but a capable assistant that understands organizational context and proactively drives projects forward. Through deep integration with Slack, clear permission boundaries, and a consumption-based billing mechanism, Claude Tag is poised to become the core engine for upgrading enterprise productivity in the future.

Further Reading For detailed documentation and setup guides, please refer to Anthropic’s official Claude Tag Documentation and Product Page.

For speaking invitations, internal engineering sessions, or architecture exchange, see the topics and public work I can bring into the conversation.

Speaking & contact