phux docs
guides

Cockpit

Cockpit is the native macOS attach client. It talks to the same phux server the TUI does, through phux-client-ffi, so the terminals you split in one are the...

evolving document
Full source summary

Cockpit is the native macOS attach client. It talks to the same phux server the TUI does, through phux-client-ffi, so the terminals you split in one are the terminals you open in the other. It is independently versioned. This page is the human router; the in-tree app owns its build notes.

What it is

Cockpit is a native macOS application over the C ABI in phux-client-ffi. It does not run the TUI. It attaches to a running phux server and paints the same Terminal-kind resources the TUI shows: tabs, splits, focus, and input stay in the app; the shells stay in the server.

Closing a Cockpit window detaches. The session keeps running. Reopening reattaches to the same durable work.

Install

Apple silicon, macOS 11 or later. Intel Macs have no release artifact; the curl installer and the cask both refuse there.

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

or the Homebrew cask:

brew trust --tap no-phux/tap
brew tap no-phux/tap
brew install --cask no-phux/tap/phux-cockpit

Full installer notes, including pinning a cockpit-vX.Y.Z tag, live in ../INSTALL.md.

Authority

Same server, same terminals as the TUI. Cockpit is a peer consumer, not a second multiplexer and not a second process-owning daemon. Its release cadence is independent of the CLI: cockpit-vX.Y.Z tags, not the phux binary’s.

This tree projects AgentSession resources as rows under their parent terminal, not as panes. Maturity of the rest of the product is in ../CONCEPTS.md.

Limits

  • macOS Apple silicon only.
  • Independently versioned from the CLI; install both when you want both.
  • Direct local PTY sessions in the app are ephemeral and die with it. Durable work uses the phux server.

Build

The in-tree app, including how to build it, is ../../clients/cockpit/README.md.

View exact source