Sign in Subscribe
news

Claude Tag

Claude Tag is Anthropic's way for teams to work with Claude as a teammate inside Slack. Announced June 23, 2026 (beta for Claude Team and Enterprise), it lets Claude join Slack as a team member: admins grant it access to selected channels, tools, data, and codebases, and anyone in a channel can tag

Sebastien Dubois

Sebastien Dubois

— 4 min read

Canonical version: Claude Tag.

Claude Tag is Anthropic's way for teams to work with Claude as a teammate inside Slack. Announced June 23, 2026 (beta for Claude Team and Enterprise), it lets Claude join Slack as a team member: admins grant it access to selected channels, tools, data, and codebases, and anyone in a channel can tag @Claude to delegate tasks while they focus on other work. It runs on Opus 4.8 and replaces the previous Claude in Slack app.

Anthropic frames it as the next evolution of Claude Code: more proactive, and built for a full team rather than a single user. Internally, 65% of Anthropic's product team code is written by their internal version of Claude Tag — including most of Claude Tag itself — and the pattern has spread beyond engineering to chasing product metrics, working support tickets, and root-causing bugs.

What makes it different

  • Multiplayer: one Claude per channel interacts with everyone. Anyone can see what it's working on and pick up the conversation where the last person left off — closer to a teammate than a private chat.
  • Learns over time: it builds context from the channels it follows, so nobody has to re-explain things. With permission it can also learn from other channels and data sources (it doesn't report from private channels).
  • Takes initiative: with "ambient" behavior enabled, it proactively flags relevant information and follows up on threads or tasks that went quiet without resolution.
  • Works asynchronously: set it a task and move on. It can schedule tasks for itself and pursue a project autonomously over hours or days — enabling delegation to many Claudes in parallel.
  • DMs: message it directly and it responds privately, using your personal tools and connectors.

Identity, permissions, and memory model

  • Admins define which tools and data Claude can access, per channel — effectively separate Claude identities per use. Memories stay scoped: a sales Claude won't pass memories to an engineering Claude, nor leak data across scopes.
  • Two memory tiers: a workspace-wide shared tier that carries across channels, and a per-channel tier that stays local. Channel-tier memory is visible to everyone in the channel, which acts as a safeguard — anyone can see and revert a bad saved rule.
  • Admins set token spend limits (org-wide and per channel) and get an audit log of everything @Claude did, along with who requested each task.
  • Code runs in an isolated, ephemeral cloud container cloned per session — installed dependencies and uncommitted files don't persist; anything worth keeping must be committed and pushed.
  • In a channel, Claude uses shared/project credentials; personal connectors only apply in direct messages. Invoking it in-channel does not grant it your personal access.
  • Against in-channel manipulation, it applies a trust model: it distinguishes genuine directives from banter, won't persist harmful or service-degrading instructions, and confirms before destructive actions. It also distinguishes a conversation's initiator from incoming participants, and waits for resolution when people disagree rather than being commandeered.

Best practices (Thariq, Claude Code team)

  • Each Claude in each channel is different: "introduce" it to a new channel with a pinned message and instructions to remember (persona, when to respond, ...). This lands in its memory — think of it as its CLAUDE.md.
  • Create a personal channel (e.g. #yourname-claude) where you tag Claude for your own work with instructions specific to you; forward messages (like bug reports) there so your Claude handles them the way you like.
  • Ask Claude to maintain a pinned message it keeps updated with the status of everything, to avoid drowning in threads.
  • Have it react to top-level threads with status emojis (⏳ ✅ ❓ 🛑) so state is visible at a glance.
  • Get creative with dedicated channels — e.g. a "scheduling" channel where people tag Claude to find time on calendars.

Slack's official account called this thread "a masterclass in setting up stateful agent workflows".

How Anthropic uses it internally

  • Incident response: tag Claude in the incident thread; it pulls graphs, diffs the deploy, and comes back with root cause and the author tagged. The team approves in-thread; Claude opens the fix, lands it, watches the metric recover, and resolves the page.
  • Bug triage: Claude sits in the feedback channel and picks up reports automatically — finds the code path, reproduces, git-blames, writes a fix, and tags the owner. Only code review remains before it merges the PR.
  • Dependent work: hand it work blocked on something else (e.g. wiring up the frontend once the backend ships). It waits, watches, and shows up days later with the PR adjusted for whatever changed in review.
  • Background watchers: give it a threshold instead of a dashboard ("ping when CI stays red too long"). It stays quiet until the threshold is crossed, then posts with the failing test and culprit commit attached.
  • Launch and metric watching: point it at an A/B test with the metric and guardrails; it flags when a guardrail moves, accepts mid-run corrections, and pings when the result is significant — rollout PR ready.

Reception

  • The multiplayer aspect was widely seen as the real differentiator versus single-user agents.
  • Concerns raised on Hacker News: coworkers derailing an in-progress session, privacy when feeding information to a shared agent (mitigated by per-channel Claudes and per-channel access config), and machine-identity attribution — e.g. GitHub actions go through a single app identity, so audit logs can't distinguish which channel's Claude acted.
  • Skeptics called it "a brand name for tagging a Slack app" and noted Anthropic's rapid-fire product launches.
  • Compared to ChatGPT Workspace Agents: similar concept, but admin-configured per channel, more technical setup, and always named "Claude".
  • It fits the broader "loop engineering" trend — delegating recurring work to standing agent loops with shared knowledge layers, logging, and verification (open-source templates and skills for finding delegation opportunities appeared the same week).

References

About Sébastien

I'm Sébastien Dubois, and I'm on a mission to help knowledge workers escape information overload. After 20+ years in IT and seeing too many brilliant minds drowning in digital chaos, I've decided to help people build systems that actually work. Through the Knowii Community, my courses, products & services and my Website/Newsletter, I share practical and battle-tested systems.

I write about Knowledge Work, Personal Knowledge Management, Note-taking, Lifelong Learning, Personal Organization, Productivity, and more. I also craft lovely digital products and tools.

If you want to follow my work, then become a member and join our community.

Ready to get to the next level?

If you're tired of information overwhelm and ready to build a reliable knowledge system:

Found this valuable? Share it with someone who needs it.

Join 6,000+ readers. Get practical systems for knowledge & AI. Free.

Subscribe ✨

Free: Knowledge System Checklist

A clear roadmap to building your own knowledge system. Subscribe and get it straight to your inbox.

6,000+ readers. No spam. Unsubscribe anytime.