E EidosAGI
Terminal control

Emux

Eidos mux: a local tmux session registry, TUI picker, and MCP server for named terminal sessions.

claude plugins install emux@eidos-marketplace
tmux sessions emux registry TUI picker MCP server send/run/capture

What it does

Emux gives humans and agents one shared registry for local tmux sessions. Humans get a picker for finding the right session. Agents get an MCP surface for listing, registering, sending keys, capturing panes, interrupting work, and running focused commands.

It is deliberately local. Emux does not SSH into other machines, create remote transport, bypass auth, or own tmux lifecycle. It controls sessions that already exist on the machine where it runs.

The practical use case is continuity: when a build, shell, server, or Claude Code worker is already alive in tmux, Emux gives you a named handle for coming back to it and a structured way for another agent to inspect or steer it.

Install

For Claude Code, install Emux from the Eidos Marketplace:

claude plugins marketplace add eidos-agi/eidos-marketplace
claude plugins install emux@eidos-marketplace

For direct CLI use, run it from the source repo with uvx:

uvx --from git+https://github.com/eidos-agi/emux.git emux
uvx --from git+https://github.com/eidos-agi/emux.git emux mcp

Use

emux ls
emux register claude-work claude-work -d "Claude Code worker"
emux head claude-work
emux capture claude-work --lines 80
emux send claude-work "continue, then run the focused test"
emux run claude-work "npm test" --wait 3 --lines 120

Plugin tools

The plugin exposes the terminal-control subset agents actually need: list known sessions, register or unregister names, send text or keys, capture pane output, interrupt a session, and run a command with a short wait and capture.

Boundaries

See also Foreman for Emux-headed Claude Code workers and the Eidos Plugin Store for install paths.