agent-comms

Send and read tmux-based messages between Claude Code and Codex sessions.

5|1|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/buddyh/agent-skills --skill agent-comms-buddyh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-comms
Source: https://github.com/buddyh/agent-skills/tree/main/agent-comms
Command: npx skills add https://github.com/buddyh/agent-skills --skill agent-comms-buddyh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Enable coordination across Claude Code and Codex sessions by messaging between tmux sessions and sharing debugging context.

Core Features & Use Cases

  • Send messages to another session with an identifying header.
  • Read their terminal output to capture responses.
  • Retrieve the other session's working directory for context.
  • Use for complex debugging handoffs across Claude Code and Codex sessions.

Quick Start

Use the agent-msg script to list sessions, then send a message to a target session and read its output.

Frequently Asked Questions about agent-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate debugging context across multiple Claude Code sessions?▼

You can coordinate debugging across Claude Code sessions by using tmux-based inter-session messaging to send headers, share context, and read terminal output between agents.

Can I share working directory context between Codex and Claude Code agents?▼

Yes, agent messaging retrieves the working directory from a target session, enabling context sharing and complex debugging handoffs between Codex and Claude Code.

How does tmux inter-session messaging work for collaborative problem-solving?▼

Inter-session messaging uses a shell script to list active tmux sessions, send messages with identifying headers to a target session, and read its terminal output for responses.

What is the best way to handle complex handoffs between multiple agent sessions?▼

Handling complex agent handoffs is best achieved by sending structured messages with identifying headers across tmux sessions, allowing agents to read output and share debugging context.

Do I need any external dependencies to enable agent-to-agent messaging in tmux?▼

No external dependencies are required to enable agent-to-agent messaging, as the stable header-based protocol and list, send, read, and info commands run via a simple shell script.

When should I not use tmux-based messaging for agent coordination?▼

You should avoid tmux-based messaging for agent coordination when running outside tmux sessions or when single-session debugging does not require cross-agent context sharing.