How to have your Claude Code sessions message each other so findings and status move between terminals without you copy-pasting.

Use this when you run several sessions at once, such as parallel worktrees on one repository, and one learns something another needs; 📝Claude Code Cross-Session Messaging covers the safety limits.

What You'll Need

• Claude Code v2.1.224 or later on macOS or Linux (v2.1.234 on native Windows), in each session
• Remote Control connected, only if a session runs on another machine or in the cloud

Steps

1. Check your version — Run claude --version in each terminal and claude update if it's older. Messaging turns on by itself once the version qualifies.
1. Name your sessions — Run /rename api-worker in one session and give each other session its own short name. Peers address a session by this name.
1. See who's reachable — Run /list-agents (or /peers). The first line is this session's own name, and the rows below are the sessions Claude can message.
1. Send a message — Type a prompt such as "Let @api-worker know users.name is now users.display_name." Claude writes the message and delivers it with SendMessage.
1. Read what arrives — Watch for a dim line starting "Message from @…" in the receiving session. Press Ctrl+O to read the full text; Claude reads all of it either way.
1. Ask for a done signal — Type "Tell me when the migration session finishes what it's working on." You get one notice when that session next goes idle.
1. Set inbound rules — Run /config and choose accept, hold, or refuse under Messages from your other sessions. Hold shows each message for approval first.

What's Next?

• 📝Claude Code Agent View — dispatch the background sessions you'll message
• 📝The Agent Worktree System — keep parallel sessions on separate checkouts
• 📝Claude Code Multi-Agent Orchestration — compare every way to run Claude in parallel

Contexts

• 🏷️#claude-code
• 🏷️#claude-code-lexicon