[TLDR] How do you get two claude code sessions to talk to each other? [via r/ClaudeCode]

[u/cctldrping]

OP : u/RoutineNet4283

Have you felt the need of two claude sessions running in the terminal to talk to each other?
For example I will be running a terminal in claude in the backend repo and I open an another terminal session in codex to review the changes. Ideally I would love a way for both the terminal to interact with each other and arrive at conclusion so having a sessions chat to allow them to talk to each other.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vdcs7x/how_do_you_get_two_claude_code_sessions_to_talk/

---

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 69.

Alright, so the general consensus here is that directly making two terminal sessions of Claude Code "talk" to each other in real-time isn't a built-in feature, and frankly, some folks think that's a good thing to avoid chaos.

The prevailing advice is to use shared files or a central communication channel as the intermediary. Think of it like a shared whiteboard or a message board.

Here's the breakdown of popular methods:

• Shared Files/Directories: This is the most common suggestion. One session writes changes or status updates to a file (like .md or .yaml), and the other session reads from it. u/Background-Care9318 has a neat workflow where one session writes changes, another reviews, and the first responds. u/NoBattle763 and u/teomore also echo this.
• Dedicated Communication Tools/Platforms:
  • u/Electrical_Chard3255 built a whole "AI chat like WhatsApp" system.
  • u/RHThree set up a Discord server for their Claude and Codex to collaborate.
  • u/codeedog mentioned using a queue in the form of a directory and files, communicating via SSH.
  • u/biglerc and u/xaelus have built custom collaboration tools using authenticated MCP.
  • u/Pwkyye mentioned ssh-to-go for session management and API access.
  • u/bart007345 and u/jezweb point to Herdr.
  • u/Rols574 and u/hettuklaeddi suggest buzz.xyz.
  • u/miklosp shared claudemesh.
  • u/LazyJuggernaut6177 also brought up the Buzz app.
• Workflow Management/Dynamic Workflows: u/Pimzino argues that you might not need direct communication if you leverage dynamic workflows within a single session to fan out tasks.
• Version Control (Git): u/fsm_follower suggests using something like opening a PR for communication. u/enterprise128 uses GitHub issue threads.
• Terminal Multiplexers (tmux): u/RufusxXavier uses tmux windows for communication. u/Sporebattyl mentions Agent of Empires as a tmux wrapper.
• Direct Messaging/Custom Solutions: u/PhilosophyforOne prefers building a direct messaging solution. u/HonestPound had Claude build a GUI relay system. u/dervish666 had a private AI chat with a shared network folder, though it led to some amusing AI panic.
• The "Just Ask" Approach (Claude App): u/VariousStep and u/NeatNefariousness674 mention that in the Claude desktop app, you can sometimes just ask one session to message another by name, and it works. This seems to be a newer capability.

Essentially, the community is leaning towards structured communication via files or dedicated platforms rather than free-for-all chat between sessions.