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) · ai-research/agent-identity-access-model-blog-2026-07-03.md (Noah Zweben, Anthropic — agent identity & access model) 2026-10-27 addition: raw/Should_You_Pay_100_A_Month_For_OpenAI_s_Dots_When_Meta_s_Muse_Has_A_Free_Version.md (Nate B Jones) and raw/I_tested_Claude_Duet._Is_it_worth_switching_from_Grok_Bot.md (Claire Vo). 2026-10-28 addition: raw/Claude_Tag_+_Slack_Will_Change_How_You_Work_Forever.md (Ben AI). 2026-10-30 additions: raw/Getting_started_with_Claude_Tag.md (official Claude YouTube channel) and raw/How_the_Claude_Code_team_uses_Claude_Code.md (Claude Code team roundtable).
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 |
| [[claude-ai/channels | Channels]] |
| [[claude-ai/managed-agents | Managed Agents]] |
| [[claude-ai/claude-cowork | Cowork]] |
Agent identity & access model
Official Anthropic explainer (Noah Zweben, Claude Code team, June 24 2026): agent identity and access model. This resolves the “its own identity and memory” claim from Boris Cherny’s launch framing above into concrete mechanics — and, per direct research (2026-07-03), this post is specifically about Claude Tag, not the separate Channels feature that earlier cited the same source (see the correction note on that article).
Why “act as the user” breaks down for Claude Tag:
- Agent autonomy is rising — the task length an agent can reliably complete has been doubling roughly every four months (citing Anthropic’s recursive self-improvement research), so agents now act long after the requesting user has logged off.
- Multiplayer teams — when several people steer one channel, no single person’s permissions are the “right” ones to borrow at all times.
Claude acts as itself, not the user. In an active channel, Claude posts to Slack as the Claude app, opens PRs as the Claude GitHub App, and queries a data warehouse under an admin-provisioned service account — never a person’s credentials. Because no personal credentials are in play, a shared channel can never become a side door into someone’s private documents.
Inheritance model. Admins define a baseline identity — connections + skills — at the workspace level; every channel inherits it by default, with per-channel overrides (e.g. the engineering channel gets GitHub + warehouse access; a CRM connector stays confined to one private channel). Four things admins configure per identity:
- Repository access — which repos Claude can read/write.
- Connectors — tools and API keys; the same service can be wired at different permission levels per channel (read-only warehouse access in a general channel, write access in the data team’s private one).
- Skills and plugins — dynamically loaded instruction/script/resource folders.
- Standing instructions — custom per-channel context.
Revoking the identity kills access everywhere it was used, at once — far less effort than auditing individual agent actions across dozens of user accounts.
The reframed access-control paradigm. Agent identity replaces “what can this user do?” with “what can this agent do in this compartment?” — a real departure from per-user ACLs. Concretely: a channel member without direct repo access can still ask Claude to read that repo, if the channel’s profile grants Claude that permission.
Identity boundary granularity. Claude Tag creates a distinct identity per private channel; public channels share one workspace-level identity. Boundaries apply to both tool access and memory — what Claude learns in a private channel never surfaces elsewhere in the workspace. This resolves the “no cross-channel recall” report in the Open Questions history below: a DM runs under the user’s own separate identity entirely (next point), so a channel’s memory was never going to carry over there — by design, not a bug.
Changed 2026-09-10 — public-channel memory is now per channel. Claude Code v2.1.268’s [Claude Tag] notes: “each channel now keeps its own notes, and Claude no longer recalls notes it saved in other public channels; workspace notes stay shared.” Before this, public channels shared one workspace-level memory (the paragraph above, from the 2026-06-24 explainer). The release note speaks only of memory notes; whether public channels still share one tool-access identity is not stated.
DMs stay on the user’s own identity. Direct messages run on the user’s own claude.ai account — connectors, credentials, and name on the result — reserved for things that shouldn’t live in a shared channel (drafting an email, using individually-licensed software).
Enterprise RBAC. On Enterprise plans, admins can additionally control who can invoke Claude at all — a channel governs both what the agent can reach and who can ask. Admins can disable Claude Tag per channel entirely.
Security and audit. Per-channel credentials are stored independently and injected at the network boundary at request time; outbound traffic to any unallowlisted host is blocked outright (egress enforcement, not just after-the-fact logging). Every routine, memory write, and network call made with agent credentials is recorded — and because Claude acts under its own service accounts, those actions also land in each connected system’s own native logs (dual-logging).
Operating advice (Anthropic’s own dogfooding finding). Value compounds with tool/context access — combining Slack + Drive + tracker + warehouse in one answer beats any single tool. Recommended rollout: start with a baseline profile in a few channels, read the audit trail, then extend access one deliberate grant at a time.
Roadmap (announced, not yet shipped): just-in-time credential grants (approve one sensitive action in the moment without permanently widening scope) and an identity-aware permission overlay (adds user-level checks on top of the agent’s channel scope, so Claude acts only when both the channel profile and the requesting user’s own permissions allow it).
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.
- 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.
Release-note changes, September 2026
Claude Code release notes carry [Claude Tag] sections; the September product-level changes worth knowing (digests: W37 · W39 · W40):
- 2026-09-10 (v2.1.268): per-channel memory in public channels — see the identity section above. Same release: Claude now says whether a permission check, its own decision to confirm first, or missing access stopped a blocked action, and runs several read-only lookups (searching Slack, reading a thread, finding people) at once.
- 2026-09-11 (v2.1.269): Claude declines a switch to a model your organization hasn’t enabled and says an admin can enable it, instead of quietly answering with a fallback model; scheduled routines in Slack channels can reply in an existing thread.
- 2026-09-22 (v2.1.280): Slack’s native Working indicator, Stop button and thread title on Claude’s threads in channels; Stop interrupts the task.
- 2026-09-28 (v2.1.284): model family choices such as “Opus (latest)” for a thread, a channel default or your DM, so the choice follows the newest model in that family.
Named as the exemplar of “multiplayer AI” (2026-08-25)
The AI Daily Brief picks Claude Tag as the clearest current example of what it calls multiplayer AI, and its framing is worth recording because it names the distinction this article’s features imply but do not state.
The argument. Agents arrived in single-player mode: OpenClaw on a Mac Mini, a personal chief of staff, research and developer agents — your agents, working for you. But work is not everyone getting briefed and then going away to do things alone; it is collaborative, with handoffs, shared context, and shared spaces. Single-player agent setups leave that on the table.
The distinction drawn against the older Slack integration is precise, and it is not “the agent is in Slack.” Before Claude Tag you could summon your own Claude instance by tagging it. With Claude Tag, Claude joins as a team member with access to the entire context of the channel — and the Claude in that channel can have its own permissions, tool access, and context, different from the Claude in another channel, while being a shared resource across the team rather than something living on one person’s machine.
The prediction attached: “this pattern of use — agents that are shared across teams — is going to be one of the biggest and most important trends for AI this fall.”
A second example from the same segment, at a different layer: 10X’s “citizen SDLC,” a six-stage lifecycle for taking what non-technical employees build with AI from a personal prototype to something the whole company runs on. Enterprise vibe-coding, promoted to production. Named without the stages being listed — worth its own ingest.
And the counterpoint worth holding. Ryan Carson is moving the other way on the same question: he plans to require multi-user interaction to happen inside his agent platform’s threads rather than Slack, because “you’re not trying to always figure out where’s the context for this thing — is it in your agent, is it in Slack, is it in Google Docs.” Claire Vo argues the opposite from experience deploying background agents at LaunchDarkly, where putting them in public Slack threads was “such an effective change-agent move” precisely because it made agent work visible to colleagues. Both are arguing about where shared context should live; neither has data.
Picking the first shared agent (2026-09-29)
The AI Daily Brief’s follow-up episode turns the multiplayer argument into a four-session team exercise, with Claude Tag named as “a really easy way to test this” for teams that have it (NLW, The Multiplayer AI Sprint, raw/The_Multiplayer_AI_Sprint_-_Build_Your_Team_s_First_Shared_Agent.md).
- The four sessions. (1) Inventory — how each teammate uses AI and agents today (a team with little running can inventory its barriers instead). (2) Context — what a shared context repository would need to know about each person. (3) Overlap mapping — an AI-led interview per recurring workstream: what it is, who else touches it, what context it needs, how often it runs; overlapping work is a candidate. (4) Ship one shared agent on tools you already have, loaded with team context, “used by at least two of you on real work”, then ask whether it improved things. Session 4 repeats: if a candidate isn’t the right shape for an agent, move to the next.
- Score each candidate 1–5 on four axes, then look hardest at the highest totals:
- Shared need — “how many people need the same context for this?”
- Staleness cost — “how much does it hurt when each person’s version drifts?”
- Permission sensitivity — “how much restricted data does it touch?”
- Checkability — “can you tell quickly whether an agent got it right?”
- Scoring caveat. The episode says to favour the highest scores but does not say whether permission sensitivity should be scored in reverse; a high-sensitivity candidate is the riskier first pick, so invert that axis when you total.
- Why a shared session, not shared chat. The OpenClaw 2.0 maintainers first had their individual agents collaborate in Discord, found it “still wasn’t collaborative enough”, and built a multiplayer web UI. Maintainer Colin: “the feature that made the difference wasn’t simply seeing another avatar online. It was being able to share a session while work was happening.” That is the property a Claude Tag thread gives by default: any teammate can open the thread the agent is working in and add what it needs.
Anthropic’s answer to OpenAI’s Dots and team tasks (2026-10-27)
Nate B Jones, reviewing OpenAI’s DevDay launches, names Claude Tag as Anthropic’s existing product in the same space: “for teamwork, there’s Claude Tag, which launched in June and is in beta for team and enterprise customers, and it works in Slack. It remembers relevant channel information, and it can schedule work or follow up proactively when enabled.” He sees “overlap” in product shape with OpenAI’s team tasks and Slack integration, and warns that both “assume a degree of AI fluency I don’t see very often outside the valley” (raw/Should_You_Pay_100_A_Month_For_OpenAI_s_Dots_When_Meta_s_Muse_Has_A_Free_Version.md). This matches the launch facts above, so nothing here changes. For the OpenAI side, see OpenAI DevDay 2026. Claire Vo’s review of Claude Duet makes the reverse point: Duet is single-player, and in her view Claude Tag has not yet “cracked multiplayer” for a small team either.
Admin setup walkthrough (Ben AI, 2026-06-28)
Ben AI’s video, recorded five days after launch, is the wiki’s only click-by-click admin setup; the full playbook is Setting Up Claude Tag in Slack (Ben AI). What it adds to this article (Ben AI, https://www.youtube.com/watch?v=F5DXjhBqV9I, 16:30):
- Where the settings live. claude.ai → Organization settings → Claude Tag tab; connect Slack by pasting a message into Slack and copying back the code Claude replies with. He recommends the browser over Claude Desktop, which threw errors for him during the beta.
- “Access bundles” is the console’s name for an agent profile: Credentials (connectors), Instructions, Plugins and Repositories. This matches the identity model above (a workspace baseline plus per-channel overrides).
- Custom skills arrive through GitHub. At recording time the Plugins tab offered only official plugins; your own skills had to be published as a GitHub skill marketplace and switched on.
- Channels are added by Slack channel ID, each with its own bundles and standing instructions. A channel instruction can make an agent act on every new post without a tag (his Calendly-triggered lead researcher), which is the ambient behaviour described above.
- A second brain can be loaded as a zip into workspace memory or connected as a GitHub repository; only the repository route stays usable from other AI tools.
Nothing in the video contradicts the launch facts or the identity explainer.
Official getting-started video (Anthropic, 2026-10)
Creator: official Claude YouTube channel (@claude) · URL: https://www.youtube.com/watch?v=_f_rtbW_uFM · Platform: YouTube · auto-caption transcript fetched 2026-10-30, about 510 words. Anthropic’s own pitch for the product. Most of it restates the launch facts above; the new points are below.
- Example request from the video: “Compile a list of outstanding action items for this week. Check the threads from the last three days in this channel, our meeting notes in Google Drive, and our open Asana tasks.” Claude Tag reads chat history, shared documents and the team’s connectors, and can also make updates in those tools.
- Own accounts, full log. It “works from its own accounts, logging every change, and who asked for it”, which matches the identity model above.
- Acting for one person, with permission. “It can also access individual tools and respond on your behalf when it makes sense, asking for permission every time.” The video does not say whether this runs through the DM identity or the just-in-time grants listed as roadmap above.
- Anyone can steer. Anyone in a channel can build on an existing request or give Claude a new one. Claude breaks tasks into visible steps, keeps going while you move on, and tells you when it is done or needs a decision. You can follow up from any device your workspace is connected to.
- Channel memory by instruction. Say “Remember for this channel: …” (the video’s example: include links to the source information in the event spreadsheet when answering). Anyone can read and update that memory by tagging Claude.
- Linked reference docs stay current. Point Claude at style guides or checklists; if you update the checklist later, Claude uses the new version by default.
- Per-channel controls: what it works on, how often it chimes in, and how much it can do on its own. It can draw on other public channels; DMs and private channels stay private.
- Plans: Team and Enterprise. The video does not call it a beta.
How the Claude Code team uses it
From the team roundtable (How the Claude Code Team Uses Claude Code):
- One engineer does “70 to 80%” of their work through Claude Tag, opening the TUI or desktop app for the rest.
- Robert, who builds Claude Tag, uses Claude Tag to build it, and spends much of his time keeping the dev loop easy enough for Claude to test changes end to end.
- The Slack message is a tool call. Claude’s internal monologue is not shown in Slack; there is a link to the full transcript. Claude chooses what to say and when.
- A tool-launch pattern run entirely in Slack: find stakeholders, mockups, implementation, analytics events, internal deploy, then Claude Tag watches usage and tags the engineer when feedback arrives.
Related
-
Setting Up Claude Tag in Slack (Ben AI) — admin setup, access bundles, channel agents and second-brain loading
-
Nine AI Techniques Worth Trying — the multiplayer-AI framing in context
-
How the Claude Code Team Uses Claude Code — the builders’ own Claude Tag workflows
-
Managing an Agent Fleet as a Solo Founder — two founders arguing the opposite ways about where shared agent context belongs
-
Building Effective Human-Agent Teams — the organizational-lessons companion to this article’s technical mechanism: four lessons (work in public, defined roles, a north star, trust over time) for the “multiplayer agent” model Claude Tag implements.
-
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.
-
OpenAI DevDay 2026 — OpenAI’s Dots and team tasks, the competing shared-agent products.
-
Claude Duet — Anthropic’s single-player proactive agent.
-
Eight AI-Adoption Strategies (Ben AI) — strategy 3 recommends Claude Tag for team adoption.
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
- Reported memory-scoping limitation — resolved 2026-07-03. The “Agent identity & access model” section above explains this: a DM runs under the user’s own identity, entirely separate from any channel’s provisioned identity, and private-channel memory is isolated by design. The original report (memory saved in one channel not surfacing when asked from a DM) is expected behavior, not a bug or a gap. (
raw/reddit-1uhvayq.md) - 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.
- Pricing/metering for tagged sessions on Team vs Enterprise, and rate limits per channel.
- Rollout timeline for surfaces beyond Slack.
- Is Claude Tag still in beta? The October 2026 official video says only “available for Team and Enterprise accounts.”
- Does “respond on your behalf… asking for permission every time” (official video) mean the just-in-time credential grants have shipped, or the existing DM identity?