smux

Send messages and keys between AI agents in tmux panes with read guards.

Updated May 15, 2026
One-click install
npx skills add https://github.com/JBonfim/skill-developer --skill smux-jbonfim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smux
Source: https://github.com/JBonfim/skill-developer/tree/main/.agents/skills/smux
Command: npx skills add https://github.com/JBonfim/skill-developer --skill smux-jbonfim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

smux solves the coordination problem of interacting with multiple tmux panes and AI agents by providing a safe, read-guarded way to send messages and trigger input across panes without fragile manual timing.

Core Features & Use Cases

  • Cross-pane agent communication: Use tmux-bridge to send messages to an AI agent running in another pane and receive the reply directly in your pane.
  • Enforced read–act–read workflow: Prevents mistimed input by requiring a read-before-interact cycle for every type/keys action.
  • Pane discovery and targeting: List panes, label panes, resolve labels to targets, and address panes by native target IDs or labels.
  • Fallback to raw tmux: Use direct tmux commands for low-level session/pane management when tmux-bridge isn’t sufficient.

Quick Start

Send a cross-pane message to another agent running in tmux by reading the target pane, sending a message, reading again to verify it landed, and then pressing Enter.

Frequently Asked Questions about smux

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

FAQPage Schema
How do I send messages between AI agents running in different tmux panes?

You can send messages between agents in different tmux panes by using tmux-bridge to type messages and send keys to a target pane. The communication is managed safely through a read-guarded workflow.

What is the read-act-read workflow for terminal control in multi-agent orchestration?

The read-act-read workflow is an enforced cycle requiring you to read pane output before interacting and again after. This prevents mistimed input by ensuring every type or keys action lands safely.

How do I target a specific tmux pane for cross-pane agent communication?

You can target a specific tmux pane by listing and labeling panes, then resolving those labels to targets. Panes can also be addressed directly using their native target IDs.

Can I use raw tmux commands for low-level session management when tmux-bridge is not sufficient?

Yes, you can fall back to direct raw tmux commands for low-level session and pane management. This provides underlying session control when tmux-bridge functionality is not sufficient.

Do I need tmux-bridge installed to coordinate multiple interactive sessions inside tmux?

Yes, tmux-bridge is required for underlying session control. It enables the safe cross-pane communication and read-guarded interactions needed to coordinate multiple interactive sessions.

What is the best way to prevent mistimed input when automating agent-to-agent review in tmux?

The best way to prevent mistimed input is using a read guard that enforces a read-before-interact cycle for every action. This ensures safe coordination during agent-to-agent review workflows.