Source: raw/reddit-1udn7zy.md (@ClaudeOfficial launch post, claude.com/product/tag) · raw/x-account-claudeai-2069468693017268244.md (@claudeai) · raw/x-account-bcherny-2069474689819480394.md (Boris Cherny — sandboxing detail) · raw/anthropic-watch-claude-code-tag-v2-1-187.md + v2.1.186 (release notes) Type: Product Feature (beta) · Product: Claude Code · Announced: 2026-06-23 · Plans: Claude Enterprise + Team
Claude Tag is a proactive, team-oriented evolution of Claude Code that lets a whole team delegate work to Claude by @-tagging it in Slack, where it joins as a persistent team member with access to the channels and tools you grant it. Announced June 23, 2026 in beta for Enterprise and Team plans (starting in Slack, more surfaces planned), it is the successor to the earlier “Claude in Slack” reach-out — tagging Claude is now described as one of the main ways Anthropic itself ships, with 65% of its product team’s code coming from the internal version.
What it does
- Tag to delegate. @-tag Claude with a request in a channel and it decomposes the task into stages, uses the tools it’s been granted, works in-thread, and delivers outputs — writing or merging pull requests, running data analysis, or helping resolve an incident.
- Builds shared context over time. One Claude follows a channel and accumulates understanding of the work, so teammates don’t re-explain from scratch and can pick up a thread seamlessly. With permission it can also learn from other Slack channels and connected data sources.
- Optional ambient behavior. Turned on, Claude takes initiative without being prompted — flagging a thread that went quiet, or surfacing what’s relevant across the channels and tools it’s connected to.
- Artifacts as output. Beyond text it can produce live, interactive outputs (e.g. PR walkthroughs, dashboards) derived from full session context. ^[inferred] (the artifacts-in-Slack framing comes from the launch thread synthesis, not the official post verbatim — verify against claude.com/product/tag).
How it runs (per-thread sandbox)
Boris Cherny (Claude Code creator) described the mechanics: tagging Claude spins up a per-thread sandboxed instance with isolated memory and permissions. It clones the repo, writes/tests/compiles code, and returns the result in the thread. One instance per thread; the sandbox is discarded after the task completes. At launch he framed it as “proactive, multiplayer, with its own identity and memory — not just a bot in Slack.”
The June 2026 Claude Code releases ship the controls that back this isolation:
sandbox.credentialssetting (v2.1.187) — blocks sandboxed commands from reading credential files and secret environment variables, so a tagged-in agent operating in a shared channel can’t exfiltrate secrets through its sandbox.- Org-configured model restrictions (v2.1.187) — admins can restrict which models the picker /
--model/ANTHROPIC_MODELmay select, surfaced as a “restricted by your organization’s settings” message. claude mcp login/logout(v2.1.186) — CLI-level MCP auth (with--no-browserSSH support), part of granting a team agent scoped access to connected tools.
This is the architectural complement to the marketing framing: Claude Tag is Claude Code made multiplayer, with the isolation/permission surface hardened for a shared workspace.
How it compares to the other reach-outs
| Surface | What it is |
|---|---|
| Claude Tag | Persistent team member in Slack; @-tag to delegate multi-stage work; per-thread sandbox; optional proactive/ambient behavior |
| Claude in Slack (predecessor) | One-off @Claude mention spawns a web session from conversation context |
| Channels | External systems push events into your already-running local session |
| Managed Agents | Fully unattended cloud agents with scheduled runs |
| Cowork | Non-technical, chat-first agent surface for business workflows |
Framing and operator patterns
Creator coverage (Ron’s “5 Ways…”, the AI Daily Brief) relays the wider reception:
- Andrej Karpathy framed Claude Tag as the “third major redesign of LLM UI/UX” ^[inferred] — (1) a website you go to, (2) an app you download, (3) a self-contained, persistent, asynchronous entity with org-wide tools working alongside humans. He clarified it’s “an org-level harness,” not a Slackbot or a Claude.ai clone.
- Setup patterns from the Claude Code team (Tariq): introduce Claude to a channel with a pinned instruction message that behaves like a channel-level
CLAUDE.md(it enters memory); keep a personal channel (e.g.yourname-claude) for your own forwarded work; have Claude maintain a pinned status message with emoji workstream states. - Reported field behavior: beyond PRs/analysis/incidents it has handled bug triage, dependent/blocked work, and background metric monitoring; one operator (Chris Taylor, Fractional) reports it self-fixed a misfiring scheduled task and built its own bug tracker. ^[inferred]
- Critiques worth holding: accumulating company context inside one vendor is lock-in (“looks like convenience until you try to cancel”); dropping an always-watching agent into a shared channel raises a team-trust / “surveillance” dynamic; and a DIY alternative (a self-hosted Slack agent via Claude Code headless mode, or any model) avoids lock-in and the beta waitlist at the cost of the integration work. Prior art includes Perplexity’s Comet co-worker and ChatGPT workspace agents in Slack.
Key Takeaways
- Claude Tag = Claude Code, made proactive and multiplayer. @-tag it in Slack; it joins a channel as a persistent member, decomposes tasks, uses granted tools, and ships PRs / analysis / incident help in-thread.
- Beta on Enterprise + Team plans (June 23, 2026), Slack first, more surfaces to come. Canonical page: claude.com/product/tag.
- Per-thread sandbox with isolated memory + permissions, discarded after the task (Boris Cherny) — hardened by the
sandbox.credentialssetting (v2.1.187) that blocks reading secrets. - Shared, accumulating context means teammates don’t re-explain; ambient behavior lets it take initiative on quiet threads and surface cross-channel info.
- Dogfooding signal: ~65% of Anthropic’s product-team code now comes from the internal version — the strongest adoption data point in the announcement.
Related
- Claude Code Channels — the push-based reach-out and the “Claude in Slack” predecessor Claude Tag evolves.
- Claude Managed Agents — the unattended-cloud sibling; Claude Tag is the in-team, conversational counterpart.
- Scaling Managed Agents (architecture) — the sandbox/identity/permission model Claude Tag instantiates per thread.
- Claude Code Agent Teams — multi-agent orchestration; Claude Tag brings the same idea into a Slack channel.
- Cowork — the other team-facing surface; Cowork is chat-first, Claude Tag is channel-native.
- Scheduled Tasks / Hooks — timer- and lifecycle-driven automation; ambient behavior is the proactive leg.
- Measuring AI Agent Autonomy — Anthropic’s framing for how much initiative to grant an agent.
Try It
- Check eligibility: Claude Tag is beta on Enterprise/Team plans. An admin enables it and connects Slack; see claude.com/product/tag.
- Start scoped: add Claude to one channel with a narrow tool set (e.g. a repo + CI). Tag it on a small, well-specified PR before widening access.
- Gate credentials: confirm
sandbox.credentialsis set so sandboxed commands can’t read secrets — essential in a shared channel where anyone can tag Claude. - Turn on ambient behavior deliberately once you trust the scope — it lets Claude act without a prompt, so the permission surface matters more, not less.
Open Questions
- Exact relationship between Claude Tag’s in-Slack Artifacts and the standalone “Artifacts in Claude Code / Cowork” feature (shipped ~June 18) — same engine, different surface? Confirm against the official pages.
- Per-thread agent identity: bcherny confirms Claude Tag has “its own identity and memory,” but whether that means its own provisioned credentials (its own GitHub/Linear/service accounts) rather than the tagging user’s is implied by the launch threads, not spelled out in the cited sources.
- Pricing/metering for tagged sessions on Team vs Enterprise, and rate limits per channel.
- Rollout timeline for surfaces beyond Slack.