Anthropic 推出 Claude Tag：Slack 中的多玩家异步代理

We have covered the Age of Async Agents on the podcast:There has been a wave of companies building their own background agents from Shopify to Stripe to Paradigm to Razorpay, and even Cognition’s friends Ramp have built their own coding agent with other friend Modal.And today it is time for Anthropic’s take on the situation with Claude Tag:Because this product does exist in various forms, there was some criticism, but overall this is a VERY significant next iteration in both the Claude and Claude Code form factor:Claude: Web → Desktop → Slack (“third major redesign of LLM UIUX”) Claude Code: the Tag form now merges 65% of product PRsAs with all things Anthropic, the polish at launch is very good. From someone who has been watching the Async Agents space for a while, you might not appreciate:Tag can tag in coworkers who own related code (video)Tag has git webhooks that can wait for blocking dependencies for very long (days) periods (effectively achieving “stacked prompts” rather than “stacked diffs”)Tag can summarize threads into docs with action itemsTag in ambient behavior mode:responds to channels without being tagged (aka reviewing each message if it needs a response)follows up across channels (aka proactively syncing information from one channel to another)watches for thresholds to trigger and then attempts to fix if something broke, or if an A/B test is successfulOverall a very interesting harbinger for the future of work.AI News for 6/22/2026-6/23/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews’ website lets you search all past issues. As a reminder, AINews is now a section of Latent Space. You can opt in/out of email frequencies!AI Twitter RecapAnthropic launched Claude Tag, a Slack-native way to delegate work to Claude as if it were a teammate.Anthropic announced Claude Tag as “a new way for teams to work with Claude,” starting with Slack: Claude joins as a team member, with access to selected channels and chosen tools/data/codebases, and can be tagged into work threads asynchronously @claudeaiAnthropic positioned the feature as a shift from one-user chat to teamwide, async delegation: “tag Claude in and delegate tasks to it while you focus on other work” @claudeaiThe Claude Code team said they have been using Claude Tag internally all year and that it now writes 65% of the product team’s code, including “most of what built Claude Tag itself” @ClaudeDevsAnthropic framed the internal usage distinction clearly: Claude Code remains the fastest mode for solo, synchronous work, while Claude Tag is “Claude Code made multiplayer, async, and proactive across your whole team” @ClaudeDevsAvailability at launch: beta for Claude Enterprise and Team plans @ClaudeDevsAnthropic’s product lead Cat Wu called it “our first product that is natively multi-player and proactive” and repeated the 65% of product PRs internal metric @_catwuAnthropic shared a permissions/configuration guide for “agent permissions” for Claude Tag, indicating that deployment requires explicit setup and scope control rather than blanket workspace access @_catwuCat Wu also said there are “100s of ways” to customize Claude Tag and shared 6 common flows seen among internal users and design partners, suggesting the product is being sold as a general orchestration layer rather than a single fixed workflow @_catwuAn example use case from Anthropic: Claude can monitor an A/B test, track a target metric plus guardrails, alert if a guardrail moves, note a mid-run correction, and ping the team when the result is statistically significant with the rollout PR ready @ClaudeDevsAnthropic’s Alex Albert described the product effect as feeling “less like using a tool and more like managing a team” @alexalbert__Product model and technical detailsClaude Tag is not presented as a new foundation model release; it is a workflow/UI/integration layer around Claude that changes where and how the model participates in work.Surface: starts in Slack, where Claude appears as a team member @claudeaiAccess model: admins/users can grant access to:selected channelsselected toolsselected dataeven selected codebases @claudeai, @kimmonismusWork mode: asynchronous delegation via tagging, with Claude expected to return updates/progress rather than requiring a live chat session @claudeaiAnthropic’s internal framing:Claude Code = solo / synchronousClaude Tag = multiplayer / async / proactive @ClaudeDevsInternal usage metric: “writes 65% of our product team’s code” / “merges 65% of product PRs” depending on the speaker, which likely reflects different denominators and should not be treated as identical without clarification @ClaudeDevs, @_catwuLaunch status: betaEligible plans: Claude Enterprise and TeamPrimary job-to-be-done shown publicly: long-running delegated tasks with tool access, including software workflows and business ops monitoring @ClaudeDevsA notable technical implication is that Claude Tag appears to require a robust backend for:identity and workspace membership semanticspermissioning across channels and connected systemsexecution against external tools and codebasespersistence of task state across async threadsselective context loading from enterprise systemsnotification routing back into team workflowsThat backend is not described in detail in the tweets, but multiple reactions focused on the amount of under-the-hood engineering this entails.Facts vs. opinionsFacts explicitly stated in the tweetsClaude Tag is a new Anthropic product/workflow for teams, launched first in Slack @claudeaiClaude can be granted access to selected channels, tools, data, and codebases @claudeaiIt is in beta for Claude Enterprise and Team plans @ClaudeDevsAnthropic says the internal Claude Code team has used it all year @ClaudeDevsAnthropic employees claimed internal metrics of 65% of code written / 65% of product PRs merged @ClaudeDevs, @_catwuAnthropic gave at least one concrete example workflow: A/B test monitoring with guardrails and PR preparation @ClaudeDevsAnthropic published a Get Started guide for configuring agent permissions @_catwuOpinions / interpretations“This has completely changed how I work” and “feels less like using a tool and more like managing a team” are user-experience judgments from Anthropic staff, not externally validated productivity measurements @alexalbert__“Paradigm shift” / “third major redesign of LLM UIUX” is Andrej Karpathy’s interpretation, not Anthropic’s formal product spec @karpathy“Very useful feature” is an external positive reaction based on product description rather than hands-on public evaluation @kimmonismus“At this point it’s just marketing” is a skeptical reaction with no additional evidence attached @kimmonismus“Why even use Slack at that point?” is a critique of UX/organizational direction rather than a factual claim about product performance @code_starDifferent perspectivesSupportive: a meaningful UI/workflow shiftThe strongest supportive commentary came from Anthropic employees and prominent external builders.Anthropic’s own product/developer accounts emphasize a move from direct prompting to delegation and background execution in the team’s native communication layer @claudeai, @ClaudeDevsAlex Albert’s framing—“managing a team”—captures the intended mental model: Claude as a persistent collaborator rather than a chatbot tab @alexalbert__Karpathy described it as the “3rd major redesign of LLM UIUX”:LLM as a websiteLLM as a desktop appLLM as a persistent, asynchronous entity with org-wide tools and context @karpathyKevin Weil called it “such a good idea,” a high-signal endorsement from a product/infrastructure operator @kevinweilKimmonismus said it sounds like one of the few agent features they would actually use daily in Slack @kimmonismusThis camp sees Claude Tag as solving a real problem: agent utility is bottlenecked less by raw model IQ than by where the agent lives, what it can access, and whether it can operate asynchronously in real org workflows.N