今日は何も大きな出来事はありませんでした

a quiet day.

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 Recap

Anthropic 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 @claudeai

• Anthropic 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” @claudeai

• The 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” @ClaudeDevs

• Anthropic 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” @ClaudeDevs

• Availability at launch: beta for Claude Enterprise and Team plans @ClaudeDevs

• Anthropic’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 @_catwu

• Anthropic 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 @_catwu

• Cat 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 @_catwu

• An 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 @ClaudeDevs

• Anthropic’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 details

Claude 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 @claudeai

• Access model: admins/users can grant access to:

selected channels

• selected tools

• selected data

• even selected codebases @claudeai, @kimmonismus

• Work mode: asynchronous delegation via tagging, with Claude expected to return updates/progress rather than requiring a live chat session @claudeai

• Anthropic’s internal framing:

Claude Code = solo / synchronous

• Claude Tag = multiplayer / async / proactive @ClaudeDevs

• Internal 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, @_catwu

• Launch status: beta

• Eligible plans: Claude Enterprise and Team

• Primary job-to-be-done shown publicly: long-running delegated tasks with tool access, including software workflows and business ops monitoring @ClaudeDevs

A notable technical implication is that Claude Tag appears to require a robust backend for:

• identity and workspace membership semantics

• permissioning across channels and connected systems

• execution against external tools and codebases

• persistence of task state across async threads

• selective context loading from enterprise systems

• notification routing back into team workflows

That 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. opinions

Facts explicitly stated in the tweets

• Claude Tag is a new Anthropic product/workflow for teams, launched first in Slack @claudeai

• Claude can be granted access to selected channels, tools, data, and codebases @claudeai

• It is in beta for Claude Enterprise and Team plans @ClaudeDevs

• Anthropic says the internal Claude Code team has used it all year @ClaudeDevs

• Anthropic employees claimed internal metrics of 65% of code written / 65% of product PRs merged @ClaudeDevs, @_catwu

• Anthropic gave at least one concrete example workflow: A/B test monitoring with guardrails and PR preparation @ClaudeDevs

• Anthropic published a Get Started guide for configuring agent permissions @_catwu

Opinions / 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_star

Different perspectives

Supportive: a meaningful UI/workflow shift

The 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, @ClaudeDevs

• Alex 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 website

• LLM as a desktop app

• LLM as a persistent, asynchronous entity with org-wide tools and context @karpathy

• Kevin Weil called it “such a good idea,” a high-signal endorsement from a product/infrastructure operator @kevinweil

• Kimmonismus said it sounds like one of the few agent features they would actually use daily in Slack @kimmonismus

This 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.

Neutral/analytic: impressive if the systems work

Some reactions were positive but focused on implementation complexity.

• Karpathy’s post explicitly says the value only materializes once Anthropic solves the hard systems work around tools, integrations, compute environments, memory, security @karpathy

• Scott Stevenson generalized the point beyond Anthropic: if Slack becomes the place where humans and agents collaborate, Slack/Benioff could turn the acquisition into one of the best ever because “no other generalized AI platform has solved multiplayer well” @scottastevenson

• Joanne Jang connected the product to executive workflow reality: big-company leaders increasingly live on Slack mobile, which makes chat-native agent management a plausible UX center of gravity @joannejang

This view is less about hype and more about organizational software architecture: if agents are going to be used heavily, they need to exist inside the coordination substrate, not outside it.

Skeptical/opposing: marketing, theological UX, and Slack absurdity

Several reactions pushed back on both the framing and the product model.

• Kimmonismus also posted “At this point it’s just marketing,” likely reacting to the naming/announcement wave around Anthropic’s releases more broadly, though the timing overlapped the Claude Tag discourse @kimmonismus

• Code Star’s jab—“Why even use Slack at that point? Just have Claude talk to itself, tag itself, and build what it wants.”—highlights a core criticism: these systems risk turning human collaboration tools into agent orchestration noise @code_star

• Joanne Jang offered a more structural critique: Anthropic’s “monotheistic” product philosophy—one Claude everywhere—may become confusing in enterprises, because users don’t naturally know how to work with a single omnipresent entity across contexts @joannejang

• Her follow-up joke sharpened the critique: “wdym the Holy Spirit in the gtm channel doesn't know about reorg news from the Holy Spirit in #general ??”—a product-design complaint about identity, consistency, and memory partitioning across channels @joannejang

These skeptics are not necessarily anti-agent; they are pointing at real failure modes:

• overloaded Slack channels

• unclear accountability

• ambiguous memory boundaries

• anthropomorphic overreach

• organizational confusion around one agent identity spanning many workflows

Context: why this matters now

Claude Tag landed into an environment where “background agents,” “harnesses,” and “one person managing many agent sessions” are already emerging as the operative pattern.

Relevant surrounding tweets show a broad industry move:

• StarAgent describes an “Agent Multiplexer” for managing many Codex/Claude Code sessions across machines, built with tmux + Tailscale + web dashboard, explicitly framing one human supervising many agents @ZhihuFrontier

• Theo recommended remote-control hardware and mini PCs “for remote agent PCs,” reflecting the growing norm of long-lived background coding sessions @theo, @theo

• Mitsuhiko linked “more thoughts on looping in coding agents,” reinforcing that reliability and supervision loops are becoming first-class @mitsuhiko

• Sydney Runkle emphasized that looping agents require an engaged human in the loop so the system learns taste rather than merely amplifying bad patterns @sydneyrunkle

• LangChain/OpenHands ecosystem tweets focused on self-harness, weakness mining, eval-driven improvement, and the full agent development lifecycle, indicating a market shift from “prompting” to operationalizing, observing, and improving agents over time @hwchase17, @hwchase17, @gneubig

Against that backdrop, Claude Tag is not an isolated feature. It is Anthropic’s answer to a broader transition:

• from single-turn chat to persistent agents

• from personal copilots to team agents

• from synchronous IDE help to background organizational execution

• from model-centric UX to harness/integration-centric UX

Relationship to Claude Code and the coding-agent stack

Anthropic’s messaging repeatedly anchors Claude Tag to Claude Code, and that matters.

• Claude Code remains the core interactive coding surface

• Claude Tag extends that capability into organization-wide async workflows @ClaudeDevs

This mirrors a broader split visible across the ecosystem:

• foreground agents for direct editing and iteration

• background agents for delegated tasks, monitoring, PR prep, and long-horizon work

Multiple tweets in the broader dataset reinforce this bifurcation:

• Factory says agents run “in the background for days” across the software lifecycle @FactoryAI

• Cursor added a team marketplace for plugins/skills/MCPs, showing the harness layer becoming collaborative and organizational @cursor_ai

• OpenAI/OpenAI Devs continued pushing Codex ecosystem tooling, OSS support, mobile features, and DevDay developer coordination @OpenAIDevs, @reach_vb, @OpenAIDevs

Claude Tag’s importance is therefore partly competitive: it is Anthropic’s move to define the multiplayer async agent layer while others define IDE, router, or harness layers.

Open questions and unresolved issues

The launch tweets leave several technically important questions unanswered.

• Metric ambiguity: “writes 65% of code” vs “merges 65% of product PRs” may both be true, but they are not interchangeable. There is no denominator, no time window, and no detail on what counts as authored vs merged @ClaudeDevs, @_catwu

• Security model details: we know Claude can be granted access to selected channels/tools/data/codebases, but not:

how fine-grained the access controls are

• how secrets are handled

• what auditability exists

• how data retention works

• whether memory is scoped by channel, workspace, task, or tool @claudeai, @_catwu

• Identity model: Joanne Jang’s “monotheistic” critique points to a product design issue—should enterprises interact with one Claude or many specialized agents/personas? @joannejang

• Noise vs leverage: if Slack becomes the main surface for agent delegation, does it improve flow or create another source of interruptions and surveillance?

• Evaluation: there are no independent external evals yet in this tweet set for Claude Tag’s reliability, task completion rate, security posture, or token efficiency

Channel-lo