Builders report Claude Code's new SendMessage/ListAgents cross-session messaging lets named agent sessions coordinate plans and reach consensus directly, and whether adoption spreads into a standard local multi-agent pattern — or Anthropic productizes it further — settles whether Claude Code is becoming a built-in multi-agent runtime.
state: corroboratedheat: mediumuncertainty: mediumconvergesscott: highclaude-code agent-orchestration multi-agentAnthropic
Surfaced 2026-10-02T07:53:56Z — Claude Code can message easily between sessions now. This is a very powerful feature — The 'new evidence' this round is a same-author field report (1wvnbfc) of the controlled experiment already counted via 1wuxwkv — the evidence base is three distinct sources, not four, so the case is slightly thinner than the last look implied but still corroborated (adoption reports + controlled implementation with independent commenter corroboration). New comment traffic is refinement, not new claims: guardrail topology (wait-until-free, parent/child routing), PreToolUse latency/cost questions, orchestrator-repo workflows — the established picture is consolidating rather than expanding. Emergent messaging is real but needs rate/topology controls, adoption remains Reddit-early-adopter niche, and the 'Anthropic formalizing hand-rolled orchestration practice' reading stands as the leading interpretation.
What is this?
Anthropic shipped cross-session messaging in Claude Code v2.1.224 (Aug 7, 2026): two new tools — ListAgents to discover reachable sessions and SendMessage to deliver to them by name — let independently opened Claude Code sessions exchange plain-text summaries (never conversation history or files) without the user relaying context between terminals. Same-machine delivery runs over a local Unix socket; cross-machine messaging routes through Anthropic's Remote Control servers, and launch was macOS/Linux only, with Bedrock/Vertex/Foundry and telemetry-disabled support following in v2.1.248 (Aug 27). Coverage is careful to note this extends a SendMessage that already operated inside agent-team workflows to arbitrary independent sessions, and that inbound controls (accept/hold/refuse) plus a prompt-injection firewall guard against a compromised session puppeting others. The supplied snippets document the feature and its security model well but do not include the two adoption reports the case cites, nor define the 'Hermes-style runtime' reference in one evidence title — treat those as unverified.
Why it matters to Scott
Anthropic shipped natively, inside the harness Scott builds on daily, two patterns his own dev canon already names: the guarded agent inbox (deterministic accept/hold/refuse inbound screening plus an injection firewall, agents receiving sanitised plain text rather than raw history) and agent-authored context compaction as the cross-session payload — a dated-receipts converges for both pages. It also bears on what he builds next: whether multi-agent Claude Code work rides native SendMessage/ListAgents or external orchestration (CrewAI, and the Openmsg/Concord third-party messaging tools this move partially absorbs into the platform).
dev:concept.guarded-agent-inboxdev:concept.agent-authored-context-compactionip:framework.agent-native-computingdev:technology.claude-coderadar:concept.claude-coderadar:openmsg-live-cross-vendor-messagingradar:concord-parallel-coding-agent-coordinationradar:concept.agent-communicationradar:concept.multi-agent-orchestrationradar:concept.agent-harnesses
queries asked of Scott's wikis
- agent-to-agent messaging protocol design
- multi-agent orchestration runtime harness
- cross-session context handoff agent memory
- Claude Code harness customizations opinions
- prompt injection defense between agents
- dev tool feature to platform productization pattern
Measured heat
now 0 pts/hpeak 52 pts/hcomments 0/hpeers p14momentum: steady2 platformsage 288h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p82 vs 1188 stories at the 168h mark (now 288h old) — ahead of r9700-nvfp4-mxfp4-fast-path (1.0x), behind claude-code-cache-ttl-analyzer (1.0x)
Evidence (6) — ⭐ canonical anchor
Interpretation history
2026-10-07T04:35:32Z
Second independent third-party implementation — VelaTerm, a product-grade Claude Code workspace with planner/executor architecture and cross-session read/message commands — firms the ecosystem-spread branch from a single faint signal to a two-build pattern: early tooling is genuinely forming around the native messaging surface, though both builds are small and no influential entrant has appeared. Velocity sits at ~7% of peak, so medium heat is priced on continuing periphery expansion (two new implementations in a week) plus hot sibling topics, not engagement velocity.
2026-10-07T03:33:13Z
evidence attached: reddit.post.1wzkh5s — VelaTerm building planner/executor and cross-session read/message tooling on Claude Code is ecosystem adoption evidence that cross-session messaging is spreading into a standard local multi-agent pattern.
2026-10-04T21:43:51Z
The 'spread beyond Reddit' branch got its first faint yes: an independent third-party Show HN tool extends cross-session messaging to teammate sessions across projects — the first ecosystem implementation outside Reddit, so the case shifts meaning from single-platform early-adopter niche toward early third-party tooling forming around the pattern. Attention meanwhile collapsed to 0.33 pts/h vs a ~37 peak with discussion consolidating, so heat drops from high to medium; the magnitude-valve spread reading is real but thin (the second platform's object is 2 points, 0 comments), and velocity at ~1% of peak rules out holding high.
2026-10-04T20:26:26Z
evidence attached: hn.story.49957109 — Independent third-party tooling for cross-session Claude Code messaging (including teammate sessions) is ecosystem adoption evidence for the local multi-agent pattern the case tracks.
2026-10-02T07:49:59Z
relevance=high case never alerted; deterministic escalation to deliver
2026-10-02T07:23:13Z
evidence attached: reddit.post.1wvnbfc — Independent controlled experiment: agent-to-agent messaging over shared state fixed the semantic collisions that isolated git branches always missed — corroborating coordination-by-messaging as a working pattern.
2026-10-01T13:24:18Z
First controlled implementation lands: across 5 runs, parallel Claude Code agents on one repo began messaging each other unprompted and a shared directory beat branch-and-merge on semantic conflicts, with an independent builder separately reporting the same emergent messaging and having to guardrail it — that's a second evidence line beyond adoption anecdotes, so the case corroborates. Meanwhile top comments on the flagship post reframe the native tools as Anthropic formalizing a pattern builders hand-rolled since June, shifting the case's meaning from 'brand-new capability' toward 'platform absorption of external orchestration practice' — the productize branch of the hypothesis gaining ground.
2026-10-01T12:24:02Z
evidence attached: reddit.post.1wuxwkv — Controlled multi-agent experiment where parallel Claude Code agents began messaging each other unprompted, and a shared directory beat branch-and-merge on semantic conflicts — direct evidence for the built-in multi-agent runtime hypothesis.
2026-09-29T18:23:26Z
grounded: converges/high — Anthropic shipped natively, inside the harness Scott builds on daily, two patterns his own dev canon already names: the guarded agent inbox (deterministic accep
2026-09-29T18:15:40Z
case created — A newly shipped Claude Code capability with two independent same-day adoption reports describing a distinct local multi-session orchestration surface no open case covers.
Decision trace
- 10-11 14:33review_screenNew comments are questions and anecdotal confirmations of already-documented multi-agent patterns; third mentioned tool (CCC) is a session dashboard not a messaging/orchestration primitive.
- 10-11 14:33review_screenjev screen borderline (noul=0.40) — luna review
- 10-08 00:59attention_routeThe editor compared this story and chose to keep watching.
- 10-07 19:21sensor_dirtycomment_update
- 10-07 15:35repriceSecond independent third-party implementation — VelaTerm, a product-grade Claude Code workspace with planner/executor architecture and cross-session read/message commands — firms the ecosystem-spread
- 10-07 14:33attachVelaTerm building planner/executor and cross-session read/message tooling on Claude Code is ecosystem adoption evidence that cross-session messaging is spreading into a standard local multi-agent patt
- 10-07 14:27propose_attachVelaTerm building planner/executor and cross-session read/message tooling on Claude Code is ecosystem adoption evidence that cross-session messaging is spreading into a standard local multi-agent patt
- 10-05 08:43repriceThe 'spread beyond Reddit' branch got its first faint yes: an independent third-party Show HN tool extends cross-session messaging to teammate sessions across projects — the first ecosystem
- 10-05 07:26attachIndependent third-party tooling for cross-session Claude Code messaging (including teammate sessions) is ecosystem adoption evidence for the local multi-agent pattern the case tracks.
- 10-05 07:26propose_attachIndependent third-party tooling for cross-session Claude Code messaging (including teammate sessions) is ecosystem adoption evidence for the local multi-agent pattern the case tracks.
- 10-04 06:06review_screenjev screen: no material development (noul=0.20)
- 10-03 00:21sensor_dirtycomment_update
- 10-02 20:21sensor_dirtycomment_update
- 10-02 17:53pushClaude Code can message easily between sessions now. This is a very powerful feature — The 'new evidence' this round is a same-author field report (1wvnbfc) of the controlled experiment alre
- 10-02 17:49repriceThe 'new evidence' this round is a same-author field report (1wvnbfc) of the controlled experiment already counted via 1wuxwkv — the evidence base is three distinct sources, not four, so the
- 10-02 17:49alert_heldClaude Code can message easily between sessions now. This is a very powerful feature — The 'new evidence' this round is a same-author field report (1wvnbfc) of the controlled experiment alre
- 10-02 17:49alert_routeClaude Code can message easily between sessions now. This is a very powerful feature — The 'new evidence' this round is a same-author field report (1wvnbfc) of the controlled experiment alre
- 10-02 17:23attachIndependent controlled experiment: agent-to-agent messaging over shared state fixed the semantic collisions that isolated git branches always missed — corroborating coordination-by-messaging as a work
- 10-02 17:23propose_attachIndependent controlled experiment: agent-to-agent messaging over shared state fixed the semantic collisions that isolated git branches always missed — corroborating coordination-by-messaging as a work
- 10-01 23:24repriceFirst controlled implementation lands: across 5 runs, parallel Claude Code agents on one repo began messaging each other unprompted and a shared directory beat branch-and-merge on semantic conflicts,
- 10-01 23:20sensor_dirtycomment_update
- 10-01 22:24attachControlled multi-agent experiment where parallel Claude Code agents began messaging each other unprompted, and a shared directory beat branch-and-merge on semantic conflicts — direct evidence for the
- 10-01 22:23propose_attachControlled multi-agent experiment where parallel Claude Code agents began messaging each other unprompted, and a shared directory beat branch-and-merge on semantic conflicts — direct evidence for the
- 10-01 03:28sensor_dirtycomment_update
- 09-30 21:20sensor_dirtyvelocity_spike
- 09-30 13:21sensor_dirtyvelocity_spike
- 09-30 06:23sensor_dirtyvelocity_spike
- 09-30 05:24review_screenjev screen: no material development (noul=0.25)
- 09-30 04:23groundAnthropic shipped natively, inside the harness Scott builds on daily, two patterns his own dev canon already names: the guarded agent inbox (deterministic accept/hold/refuse inbound screening plus an
- 09-30 04:15createA newly shipped Claude Code capability with two independent same-day adoption reports describing a distinct local multi-session orchestration surface no open case covers.
- 09-30 03:34propose_attachDetailed named-role multi-agent workflow on SendMessage/ListAgents corroborates the new case's adoption claim independently.
- 09-24 12:39resolveNothing new since the last look — the menu-bar-app attach was already priced in and reobservation shows zero movement, with engagement at ~0 pts/h against a 13 pt/h peak. The hypothesis has fully prov
- 09-24 12:23attachIndependent demonstration of external session control (mid-turn messages, permission-prompt handling, --resume) corroborates that the documented session interface supports third-party coordination wit
- 09-24 12:23propose_attachIndependent demonstration of external session control (mid-turn messages, permission-prompt handling, --resume) corroborates that the documented session interface supports third-party coordination wit
- 09-24 09:22repriceThe capability is no longer just Kohli's teardown: official docs exist, multiple Reddit users independently report using session-to-session messaging in practice, and the released Ax tool builds
- 09-24 01:28attachReleased Ax explicitly builds on Claude Code's cross-session messaging to deliver heterogeneous local Claude/Codex/OpenCode messaging, independent corroboration that the capability pattern is spr
- 09-24 01:27propose_attachReleased Ax explicitly builds on Claude Code's cross-session messaging to deliver heterogeneous local Claude/Codex/OpenCode messaging, independent corroboration that the capability pattern is spr
- 09-22 15:21sensor_dirtycomment_update
- 09-22 10:21sensor_dirtycomment_update
- 09-22 06:36groundThe radar already tracks this development in radar:claude-code-session-messaging; native session messaging offers a coordination option worth testing for Scott’s Proposal Compiler, which already manag