tmux-bridge

To coordinate agent panes safely in tmux or zellij, use a compatibility interface that enforces a read-before-act cycle, requiring you to mark a target pane as safe before sending messages or pressing keys.

The read-before-act workflow for tmux pane messaging requires operators to observe and verify a target pane's status before manually typing, pressing keys, or sending messages to prevent workflow breakage and unintended actions.

Yes, you can use legacy room viewer conventions to observe agent panes across tmux sessions. A compatibility alias routes existing operator workflows to current guidance while preserving the original room execution mental model.

Yes, tmux-bridge works with zellij terminals for multi-agent coordination. It provides a compatibility interface for the room viewer layer that applies to operator workflows observing agent pane placement across both tmux sessions and zellij terminals.

You should use bridge messages instead of polling pane scrollback because operational guidance directs users to prefer canonical room status and foxctl mux list views, ensuring stable reply framing and improved traceability.

The best way to maintain consistent reply headers when messaging agent panes is to use a stable bridge message header format, which preserves consistent framing for manual replies and improves operator clarity and traceability.