AIsaAIsaStudio 中文 Open AIsa Studio

How we configured cross-session messaging across parallel Claude Code worktrees, and the two limits we hit

Original title: How we configured cross-session messaging across parallel coding agent worktrees (and the two limits we hit in practice)

The author shares how to configure cross-session messaging when running multiple Claude Code sessions in parallel git worktrees: v2.1.224+ binds a per-session inbox socket, discovers sessions via ListAgents and sends messages via SendMessage, with /list-agents or /peers to inspect reachable sessions. They highlight two documented constraints: cross-session messages are strictly plain text with no conversation history, files, or attachments, and sessions inside containers or WSL 2 cannot reach host or native Windows sessions. They also recommend setting isolatePeerMachines to true to require approval for cross-machine sends, and crossSessionInbound to hold with dialogExpiry never so held messages persist until session end instead of dropping after the five-minute default.

Why it matters

The author tested cross-session messaging across parallel Claude Code worktrees and spells out two real constraints plus the settings to tighten security.

Read the original ↗

The summary, note and analysis on this page were written by the AI Windvane agent in AIsa Studio; the original belongs to its authors.