Oh good, another terminal multiplexer for agents.

We know. This one gives a phux: it keeps your agents running, tells you which one is waiting on you, and lets a script do anything you can.

Mac, Linux & Windows · iPhone beta on TestFlight

All platforms
curl -fsSL https://phux.sh/install | sh

macOS and Linux · installs phux and phux-mcp

The phux silver fox
Real phux TUI showing coding agents and sessions in the default workspace.Real phux desktop showing the same default workspace, session sidebar, and agent tabs.
Drag to compare

Know which agent is waiting on you.

phux watches every pane. When an agent stops at a permission prompt or a question, its session moves to the top of the list, the sidebar marks it, and Ctrl-A q takes you there.

Claude CodeCodexOpenCodepiOh My PiGrokfxany CLI agent

How agent state is detected
$ phux ls
web: needs you (1 agent waiting)
api: 1 running
infra: 1 running

# or be told, instead of looking
$ phux agent wait --any --until blocked --timeout 600

Anything you can do, a script can do.

Create a pane, run a command in it, read the screen, wait for output. Every command has JSON output and a real exit code. The same operations are an MCP server, so your agents work in the terminals you can see.

Need to step in? phux take @7 gives you exclusive input. Automation cannot type into a pane you hold.

Drive terminals from scripts Give an agent the MCP server
$ phux run @1 'ls /nope'
ls: cannot access '/nope': No such file or directory
exit=2 (152ms)

$ echo $?
2

Another machine is one command.

phux sets the other machine up over the SSH access you already have. Its sessions and agents then sit next to your local ones. There is no account and no hosted service.

Remote machines
# once, from your laptop
$ phux host add me@mini

# from then on
$ phux attach mini

One lead. A visible crew.

Give a lead agent the outcome. With Crew, it places workers in isolated Git worktrees and visible panes, supervises their missions, checks their evidence, and brings back the result.

Set up Crew

Crew requires a phux source checkout, a build with native missions, Python 3.9+, and configured agents. It is coordination, not a security sandbox or a promise of unattended completion.

Example task for a configured Crew lead
Fix the flaky checkout test. Open a PR. Don’t merge it.

Workers get their own worktrees and panes. Questions and permission prompts still come to you.

Work continues while the server stays up. A server crash or machine reboot ends running programs.

Browser demo

A disposable phux shell in your browser.

Open full shell

The workspace connects when it comes into view.

Open the browser demo ↗

Limited demo shell · no sign-in

Start with one command.

curl -fsSL https://phux.sh/install | sh

Choose your platform All platforms ↗
How your workspace stays connected
Open demo

Attach from any client. The same terminals, the same output.

phux terminal

A limited demo shell, no sign-in. Try help or demo, then split a pane.