with one click
tmux-bridge
// Local terminal access via the tmux bridge. Use when the user asks about running shell commands, setting up the tmux bridge, or troubleshooting terminal connectivity.
// Local terminal access via the tmux bridge. Use when the user asks about running shell commands, setting up the tmux bridge, or troubleshooting terminal connectivity.
Plan and build Pi for Excel extensions safely: choose skill vs extension plugin vs connection, create flat SKILL.md skills, and handle API keys without asking users to paste secrets in chat.
Native Python execution via the local Python bridge. Use when the user asks about running Python locally, setting up the Python bridge, LibreOffice conversion, or troubleshooting Python connectivity.
Discover and call tools from configured MCP servers. Use when external capabilities are needed beyond built-in workbook tools.
Search the public web for up-to-date facts. Works out of the box with Jina (default, no API key needed); optionally Serper, Tavily, or Brave Search. Use when workbook context is insufficient and fresh external references are needed.
| name | tmux-bridge |
| description | Local terminal access via the tmux bridge. Use when the user asks about running shell commands, setting up the tmux bridge, or troubleshooting terminal connectivity. |
| compatibility | Requires a local tmux bridge process running on the user's machine. |
| metadata | {"tool-name":"tmux","docs":"docs/tmux-bridge-contract.md"} |
The tmux bridge gives Pi access to a real local terminal on the user's machine. The tmux tool is always registered — it just needs the bridge process running locally to work.
When the bridge is running, the tmux tool can:
pi (or other local CLIs) via tmuxThe tmux pane is a normal local shell. If pi is installed, you can invoke it directly with send_keys/send_and_capture text like any other command.
Recommended flow:
list_sessions then create_session (or reuse an existing session)command -v pipi ... commandcapture_paneFor long-running jobs, avoid rapid repeated captures. Prefer:
capture_pane with wait_ms (for example 15000-30000), orsend_and_capture with wait_for + timeout_ms when you know a completion pattern.The bridge is a local HTTPS server. Run it from a terminal:
npx pi-for-excel-tmux-bridge
This defaults to real tmux mode on https://localhost:3341.
Options:
--install-missing — auto-install tmux via Homebrew (macOS)TMUX_BRIDGE_MODE=stub — safe simulated mode (no real shell execution)TMUX_BRIDGE_TOKEN=your-secret — require auth tokenThe default bridge URL (https://localhost:3341) works automatically — no configuration required. If you need a custom URL or auth token:
/experimental tmux-bridge-url <url>
/experimental tmux-bridge-token <token>
/experimental tmux-status
The bridge uses a self-signed cert. You may need to visit https://localhost:3341 in your browser once and accept it.
The tmux tool stays registered but returns an error if the bridge is unreachable. Python tools (python_run, python_transform_range) still work via the in-browser Pyodide fallback — tmux is the only tool that strictly requires its bridge.
npx pi-for-excel-tmux-bridge.timeout_ms for longer operations.