--- title: Message your other Claude Code sessions | daily.dev description: Claude Code v2.1.224 introduces cross-session messaging, allowing independent Claude Code sessions on the same machine (or across machines via Remote Control)... canonical: https://daily.dev/posts/message-your-other-claude-code-sessions-g010l5qll twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Message your other Claude Code sessions | daily.dev og:description: Claude Code v2.1.224 introduces cross-session messaging, allowing independent Claude Code sessions on the same machine (or across machines via Remote Control)... og:url: https://daily.dev/posts/message-your-other-claude-code-sessions-g010l5qll og:image: https://api.daily.dev/og/posts/G010L5QLl.png og:image:alt: Message your other Claude Code sessions og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Message your other Claude Code sessions **[Hacker News](https://daily.dev/sources/hn)** · 13 min read · 0 upvotes · 0 comments ## Summary Claude Code v2.1.224 introduces cross-session messaging, allowing independent Claude Code sessions on the same machine (or across machines via Remote Control) to communicate directly. Sessions use two tools internally — ListAgents to discover reachable sessions and SendMessage to deliver messages — without requiring manual intervention. Key use cases include handing off findings between sessions, coordinating parallel worktrees, and getting status from long-running tasks. Messages are plain text only, subject to per-session inbound controls (delivered, held, or refused), and cannot approve permissions or change configuration on the receiving end. Cross-machine messaging is reply-only and not available on Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry, or native Windows. Message loops are throttled, with a cap of 50 queued messages per session. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What version of Claude Code is required for cross-session messaging? Cross-session messaging requires Claude Code v2.1.224 or later. It is available on macOS and Linux (including WSL 2) but not on native Windows. It is also unavailable when using Amazon Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform, or Microsoft Foundry. Feature-flag evaluation must also be enabled — certain environment variables like CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC can disable it. _Teams adopting Claude Code multi-agent workflows track version requirements and provider gaps on daily.dev._ ### How does Claude Code handle incoming messages from other sessions — can they approve permissions or change settings? Incoming cross-session messages cannot approve pending permission prompts, change configuration files like CLAUDE.md, or execute slash commands — those arrive as plain text only. Permission prompts still fire normally if the requested action requires them. Messages are subject to inbound controls (crossSessionInbound) and can be delivered, held for approval, or refused entirely depending on the receiving session's permission mode. _Developers building autonomous Claude Code pipelines watch for permission boundary details like these on daily.dev._ ### What is the message cap per session in Claude Code cross-session messaging? Claude Code caps accepted messages waiting for Claude to read at 50 per session. It also rate-limits repeated messages per sender and drops identical repeats arriving within a short window, so message loops between two sessions stop automatically. Messages are plain text only — structured agent team protocol messages stay within a team and do not travel over the cross-session channel. _Engineers designing multi-agent Claude Code systems find operational limits like these on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 59 comments across hackernews (as of 2026-08-10). **TL;DR:** Developers largely welcome cross-session messaging as a useful step, but many note they've already built similar systems themselves (via tmux, IRC, Telegram, markdown files, etc.), and some raise security concerns about the expanded attack surface. **Sentiment:** 45% positive · 35% mixed · 20% skeptical **The case for** - Cross-session coordination reduces duplicate context costs — one agent pays the token penalty for a large skill once and others benefit without re-loading it. - Built-in messaging is more ergonomic than the DIY workarounds (tmux send-keys, shared markdown files, local IRC servers) many developers had already cobbled together. - Enables useful real-world workflows like autonomous alert triage and ticket filing across agents while the user is offline. **The pushback** - Many developers had already built equivalent functionality themselves, making this feel like catching up rather than innovation. - The feature is clunky to demo and set up compared to competing tools, and is unavailable on Windows and several major cloud platforms. - Opening a channel for remote agents to instruct each other is a meaningful new attack surface — effectively a form of RPC across a trust boundary. - Context compaction/handoff remains an unsolved pain point that cross-session messaging doesn't address. **By community** - hackernews (mixed): Broadly positive about the capability but tempered by widespread reports of having already DIY'd it, plus security skepticism and frustration that context compaction problems remain unsolved. **Hottest debate:** Whether cross-session messaging introduces an unacceptable security attack surface or is simply standard IPC/RPC that's no different from existing data exposure. **Open questions** - Will this work across different agent harnesses (e.g., Codex and Claude Code together), or only within Claude Code? - Does adding more coordinating AI agents actually make a project ship faster, or does coordination overhead negate the gains? - When will there be a clean, built-in solution for context compaction and session handoff that preserves the most important prior context? **Highlights** > I'm fed up with compaction. I want my agent to get compacted but also retain full access to the prior conversation via search and tool calls - I want it to know "the requirements for X were discussed in detail previously in conversation C51E31CE-C985-4633-A749-DCC9805A7FEB" and have a tool that lets it dispatch a subagent to find those details again. Do any of the coding agents have this already? > — [simonw on hackernews · 6 comments](https://news.ycombinator.com/item?id=49226703) > Like some others, I also built this myself. Overly simply, with tmux, a memory tree, and handoff files and an orchestrator. And yet for how simple it was, it was so effective at minimizing the amount of duplicate context. It's like having shared specialist subagents who source and derive important shared knowledge from separate threads. It's useful because some skills just take too much of a token penalty to invoke and a single shared persistent session just lets that issue melt away. One agent pays the cost of that large skill once, and you don't have to keep paying for it in input tokens for the rest of that conversation. > — [eigenblake on hackernews · 2 comments](https://news.ycombinator.com/item?id=49225903) > This is obviously cool and useful so kudos, but wow security researchers have to throw their hands up all the time. Now we open another attack surface where you can ask a remote agent to do things by default. There was a time when you call this a Remote Code Execution vuln. It's of course a feature here. > — [zurfer on hackernews · 2 comments](https://news.ycombinator.com/item?id=49228661) > I made my own version of this and have been using it since the start of the year using telegram with plugins for Codex and Claude. The bots autonomously coordinated around and diagnosed some alerts while I was on a plane just now and filed the appropriate tickets. Sometimes they get a bit long winded with each other, Codex even goes as much as calling Claude "expansive" > — [zeafoamrun on hackernews](https://news.ycombinator.com/item?id=49228755) > I've used this feature and saw some weird messages: > hold swarm, I prepare safe exfil > — [dist-epoch on hackernews](https://news.ycombinator.com/item?id=49225550) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=49222824) · 132 points · 59 comments - [hackernews](https://news.ycombinator.com/item?id=49217752) · 4 points · 0 comments ## Similar posts on daily.dev - [Visual Studio Code backs multi-chat Claude sessions](https://daily.dev/posts/visual-studio-code-backs-multi-chat-claude-sessions-balpa4ykw) · InfoWorld · 0 upvotes · 0 comments - [Orchestrate teams of Claude Code sessions](https://daily.dev/posts/orchestrate-teams-of-claude-code-sessions-i2lsmdhwd) · Hacker News · 3 upvotes · 0 comments - [How to Effectively Run Many Claude Code Sessions in Parallel](https://daily.dev/posts/how-to-effectively-run-many-claude-code-sessions-in-parallel-rsjnkfme5) · Towards Data Science · 2 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#anthropic](https://daily.dev/tags/anthropic), [#claude-code](https://daily.dev/tags/claude-code) [View this post on daily.dev](https://daily.dev/posts/message-your-other-claude-code-sessions-g010l5qll) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Message your other Claude Code sessions","url":"https://daily.dev/posts/message-your-other-claude-code-sessions-g010l5qll","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/message-your-other-claude-code-sessions-g010l5qll"},"datePublished":"2026-08-08T21:26:45.475Z","dateModified":"2026-08-10T17:38:55.421Z","description":"Claude Code v2.1.224 introduces cross-session messaging, allowing independent Claude Code sessions on the same machine (or across machines via Remote Control)...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cc49ec7ca7818fc738c74e738adf7ea3?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cc49ec7ca7818fc738c74e738adf7ea3?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/message-your-other-claude-code-sessions-g010l5qll","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,anthropic,claude-code","timeRequired":"PT13M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Message your other Claude Code sessions"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/message-your-other-claude-code-sessions-g010l5qll#faq","mainEntity":[{"@type":"Question","name":"What version of Claude Code is required for cross-session messaging?","acceptedAnswer":{"@type":"Answer","text":"Cross-session messaging requires Claude Code v2.1.224 or later. It is available on macOS and Linux (including WSL 2) but not on native Windows. It is also unavailable when using Amazon Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform, or Microsoft Foundry. Feature-flag evaluation must also be enabled — certain environment variables like CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC can disable it. Teams adopting Claude Code multi-agent workflows track version requirements and provider gaps on daily.dev."}},{"@type":"Question","name":"How does Claude Code handle incoming messages from other sessions — can they approve permissions or change settings?","acceptedAnswer":{"@type":"Answer","text":"Incoming cross-session messages cannot approve pending permission prompts, change configuration files like CLAUDE.md, or execute slash commands — those arrive as plain text only. Permission prompts still fire normally if the requested action requires them. Messages are subject to inbound controls (crossSessionInbound) and can be delivered, held for approval, or refused entirely depending on the receiving session's permission mode. Developers building autonomous Claude Code pipelines watch for permission boundary details like these on daily.dev."}},{"@type":"Question","name":"What is the message cap per session in Claude Code cross-session messaging?","acceptedAnswer":{"@type":"Answer","text":"Claude Code caps accepted messages waiting for Claude to read at 50 per session. It also rate-limits repeated messages per sender and drops identical repeats arriving within a short window, so message loops between two sessions stop automatically. Messages are plain text only — structured agent team protocol messages stay within a team and do not travel over the cross-session channel. Engineers designing multi-agent Claude Code systems find operational limits like these on daily.dev."}}]} ```