More phux.
Explore the runtime, choose a client, or get release updates.
Sessions that survive
Shells run in a background server. Close the window, reattach later; nothing restarts.
Built for automation
Drive terminals from the CLI, MCP, or the public protocol. Agents report when they need you.
Every machine, every screen
Reach hosts over SSH or QUIC. Attach from a terminal, desktop, browser, or phone.
A runtime, not just a window.
Follow the work.
Switch the scenario. Follow a signal. See what stays running when everything around it changes.
Close the view. Not the work.
Your terminal lives on the machine, not inside the window you happen to be using.
Go deeper in the docsOpen a view
A client attaches to work owned by the background server.
The whole system in 16 seconds Watch the Psychopomp film
Clients and agents send structured input to the server. A PTY runs the program and emits VT bytes. Detaching a client leaves the server-owned terminal running. A federation hub exposes remote resources; their processes stay on their owning machines. The hub is a phux server role, not a required extra service.
Silent film rendered with Kit Langton’s Psychopomp. Timing is illustrative, not a latency benchmark.
Still mode: choose steps or scrub the timeline. Illustrative scenarios, not a live session. iPhone is in TestFlight beta.
Install
curl -fsSL https://phux.sh/install-desktop | shApple silicon · macOS 27 or later. Installs the CLI too, then open Phux.app. Ad-hoc signed; not Apple-notarized. Desktop install details
curl -fsSL https://phux.sh/install | shInstallers verify release checksums. More ways to install
phux for your phone
Drive the same terminals from your phone. In beta on TestFlight and Google Play.
Release updates
Release notes, occasionally. Unsubscribe any time.