Claude Code Field Guide
28 / 35

Cross-Session Messaging (New Since the Video)

Let the separate Claude sessions you're running yourself — in different worktrees or terminals — pass messages to each other.

Updated since the video
Currency check: New concept, sitting between manual worktrees and full agent teams.

The video doesn't cover this because it didn't exist yet: a middle ground between running fully independent worktree sessions yourself and setting up a full, experimental agent team. Cross-session messaging lets the separate Claude Code sessions you started — in different terminals, different worktrees — pass findings and messages to each other directly, without needing the team-lead/teammate structure or the experimental flag agent teams require.

This is the right tool when you're deliberately running parallel sessions yourself (say, one per worktree) and want them to coordinate occasionally, but don't want the token overhead or experimental status of a full agent team.

Coordinating a frontend and backend session

Two manually started worktree sessions — one building an API, one building the UI that consumes it — use cross-session messaging so the frontend session gets notified the moment the backend session finishes and changes an endpoint shape, instead of the two staying silently out of sync.

A lightweight heads-up between exploratory sessions

While researching a bug in one session, a developer has it message a second session working on a related area with what it found, avoiding duplicate investigation without setting up any formal team structure.