Claude Tag: How LLMs Became Your Colleague Overnight
Anthropic’s Claude Tag lets the Claude LLM join Slack as a team member, offering shared memory, proactive task handling, fine‑grained permission controls, internal adoption statistics, token‑based billing details, and a four‑step rollout for Enterprise and Team customers.
Anthropic announced a major update to Claude Code called Claude Tag , which allows Claude to appear in Slack as a team member that can be @‑mentioned in chats or documents. Users can invoke Claude directly to handle tasks, and the model can access tools, data sources, and code repositories after being granted channel‑level permissions.
The company positions Claude Tag as the start of the third major redesign of LLM UI/UX. The first design treated LLMs as websites, the second as desktop applications, and the third envisions them as persistent, asynchronous agents that live across an organization, retain context, and collaborate with human teammates.
Internally at Anthropic, "@Claude" has become a primary way for product teams to work: 65% of code written by the internal Claude Tag version is generated by the model, and the team reports that parallel task delegation to multiple Claudes now consumes far more time than manual execution.
Claude Tag brings several new capabilities:
Shared across the team : a single Claude instance interacts with everyone in a Slack channel, making its activity visible to all and allowing seamless hand‑offs.
Continuous learning : long‑term participation in channel discussions lets Claude accumulate work‑related context, reducing the need to repeat background information.
Proactive actions : when the “Ambient” mode is enabled, Claude pushes important information, follows up on stalled threads, and suggests next steps.
Asynchronous workflow : users hand off tasks and focus on other priorities while Claude plans, executes, and even schedules its own follow‑up work over hours or days.
Permission controls are strict: administrators assign which tools and data each Claude instance can access per channel, effectively creating separate identities for sales, engineering, etc., preventing cross‑team data leakage.
To enable Claude Tag, Enterprise or Team customers follow a four‑step process:
Pair Claude Tag with the Slack workspace.
Configure tool‑access permissions for Claude.
Set a monthly spend limit for the organization.
Test Claude in a private channel to confirm operation.
Claude Tag replaces the existing Claude‑in‑Slack app, with a migration window of 30 days. Anthropic offers introductory launch credits for eligible organizations. The feature runs on Opus 4.8 and consumes tokens proportionally to its proactive, context‑rich operations; administrators can set token‑based spend caps, and excess usage incurs standard API rates.
More information is available in the official documentation and product page linked at the end of the article.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
