tmux-cli
tmux-cli
Instructions
Use the tmux-cli command to communicate with other CLI Agents or Scripts in
other tmux panes. Do tmux-cli --help to see how to use it!
This command depends on installing the claude-code-tools. If you get an error
indicating that the command is not available, ask the user to install it using:
uv tool install claude-code-tools.
Key Commands
Execute with Exit Code Detection
Use tmux-cli execute when you need to know if a shell command succeeded or
failed:
tmux-cli execute "make test" --pane=2
# Returns JSON: {"output": "...", "exit_code": 0}
tmux-cli execute "npm install" --pane=ops:1.3 --timeout=60
# Returns exit_code=0 on success, non-zero on failure, -1 on timeout
This is useful for:
- Running builds and knowing if they passed
- Running tests and detecting pass/fail
- Multi-step automation that should abort on failure
Note: execute is for shell commands only, not for agent-to-agent chat.
For communicating with another Claude Code instance, use send + wait_idle +
capture instead.
More from pchalasani/claude-code-tools
session-search
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
34recover-context
Extract full context of the last task from the most recent parent session
34code-walk-thru
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
33patterns
Design patterns for the Langroid multi-agent LLM framework. Covers
32add-pattern
Use this skill when you learn one or more design pattern(s) in the
31voice-update
This skill should be used when the agent needs to give a spoken voice update to the user, or when reminded by a Stop hook to provide audio feedback. Use this skill to speak a short summary of what was accomplished.
27