Anthropic gives @Claude a permanent seat in your Slack channels

Anthropic has announced Claude Tag, a new product that embeds Claude directly into Slack as a persistent, shared team member — one that accumulates institutional knowledge over time, works asynchronously, and can act without being prompted.

The product, available in beta for Enterprise and Team plan customers, replaces Anthropic’s existing Claude in Slack app, which debuted in October 2025. That original integration let users DM @Claude, invoke it via an AI assistant panel, or tag it in threads for on-demand help — useful, but somewhat transactional. Then in December, Anthropic added Claude Code to Slack, letting developers tag Claude in a conversation and have it spin up a full coding session on the web, posting a pull request back into the thread on completion.

In that sense, Claude Tag does for Slack roughly what Cowork did for knowledge workers: it takes the agent loop that originated in Claude Code and extends it to a new surface and a broader set of tasks, rather than confining it to engineering workflows.

Claude Tag, in many respects, is the next step: rather than Claude joining a conversation on request and then going quiet, it now lives in the channel full-time. Tasks can be scheduled to run over hours or days, with Claude working through them independently — accumulating context, learning the vocabulary of the work, and picking up unresolved threads that would otherwise get buried.

That context isn’t necessarily confined to a single channel, either: Where administrators grant the access, Claude can draw on information from other channels to inform the work in front of it.

Sense of identity

Claude Tag effectively gives Claude its own identity in the workspace — its own accounts for every connected tool, posting to Slack as the Claude app, opening pull requests under its own GitHub app, or querying a data warehouse under a dedicated service account set up by an admin. If “ambient” behavior is enabled, Claude doesn’t need to be tagged at all — it monitors conversations, flags things it thinks the team needs to know, and follows up on threads that have gone quiet, much like the “auto” mode already familiar to Claude Code users.

Beyond scoping tool and data access, administrators can also set a ceiling on how many tokens each channel’s Claude is allowed to spend; it’s a guardrail against an autonomous agent running up costs while working unattended.

There’s one Claude per channel, shared by everyone in it, so any team member can see what’s being worked on and pick up where a colleague left off. That multiplayer dynamic is arguably one of the most significant departures from how AI assistants have hitherto worked.

For instance, a task tagged to @Claude by one person can be steered, corrected, and built upon by the rest of the team in real time.

Underpinning all of this is what Anthropic calls “agent identity” — the access construct that makes multiplayer AI possible without creating a security mess. Noah Zweben, a member of technical staff on the Claude Code team, notes in a companion blog post that this model is a necessary foundation for the kind of autonomous, team-wide work Claude Tag is designed to handle.

“The shift from single player to multiplayer AI in products like Claude Tag makes long-running, team-based work possible.”

“The shift from single player to multiplayer AI in products like Claude Tag makes long-running, team-based work possible,” Zweben writes. “Agent identity ensures that Claude’s access to tools is broad enough to be useful, but scoped enough to be secure at enterprise scale.”

In terms of how this works, Zweben explains why the traditional model — where an AI assistant borrows the permissions of whoever invoked it — needed to be rethought. Agents now schedule tasks and respond to events long after the person who asked has logged off, and in a shared channel with multiple people steering, there’s no single user whose credentials make sense to inherit.

Instead, administrators define what Claude can access at the workspace level, with each channel inheriting a baseline set of permissions that can be tightened or expanded depending on the work being done there.

“Agent identity replaces the question ‘what can this user do?’ with ‘what can this agent do in this compartment?'”

An engineering channel might get read and write access to GitHub and the data warehouse; a general channel might get read-only. Crucially, because Claude operates under its own accounts rather than anyone’s personal credentials, a shared channel can never serve as a backdoor into someone’s private documents.

“Agent identity replaces the question ‘what can this user do?’ with ‘what can this agent do in this compartment?'” Zweben writes.

Race for the Slack layer

Team messaging platforms are fast becoming the primary control layer for AI agents in the enterprise — the place where work gets assigned, monitored, and reported back on. GitHub has brought Copilot into Microsoft Teams, for instance, where OpenAI’s Codex includes a native Slack integration that lets teams delegate tasks directly from threads. And Cognition’s Devin has been built around Slack from the get-go.

Block, the Jack Dorsey-led company behind Square and Cash App, has also spent some time building something akin to this from scratch, using its open-source Goose framework to develop an agent orchestration system its engineers manage entirely from a single Slack thread.

Whichever AI ends up as the default presence in the channel where work is coordinated gains both a distribution advantage and a compounding data advantage, making it progressively harder to displace. For a company already running Claude Code in its engineering org, adding Claude Tag to its Slack channels is a natural next step — and one that deepens that dependency considerably.