Operator cockpit

Six screens. One keypress each.

zipline tui puts every pipeline, route, instance and incident in front of you, live, without opening a browser or leaving the shell. Throughput and lag redraw as the runtime moves. Pause a stalled pipeline from the row you are already looking at.

It even opens when the control plane is unreachable, and tells you why.

See the six screens Install the CLI Try the CLI in your browser
Launch

Two ways in

Run zipline tui from anywhere. Or just run zipline with no subcommand: when stdin is an interactive terminal it opens the cockpit directly, the way k9s does. When stdin is not a terminal, for example a script piping input in, it prints help instead, so nothing changes for automation.

The six screens

Everything the control plane knows

Switch with 1 through 6, or cycle with tab. Click the tabs below to see each one.

Throughput, lag, backlog and uptime across the whole runtime, with the pipelines that need attention pulled to the front.

zipline tui

Rendered from the real cockpit against demo data, not a mockup.

Keys

Keyboard first, mouse if you want it

Nothing here is a chord and nothing needs a modifier. Every key is one press.

Move around
  • 1 to 6 Jump straight to a screen
  • tab Cycle through the six screens
  • ↑↓ Move the selection within a screen
  • enter Open the selected pipeline or instance
Operate
  • p Pause the selected pipeline
  • r Resume it again
Find things
  • / Filter the current screen, on overview, pipelines and logs
  • : Command palette: fuzzy jump, or filter followed by a query
Session
  • ? Help, listing global keys and the screen's own
  • q or esc Back out a level, then confirm before quitting
The mouse works too. Tabs, rows and subtabs are all clickable.
zipline tui
The command palette. It replaces the bottom line with a single prompt, no dropdown or panel. Typing a screen name jumps there; filter followed by a query filters in place.
zipline tui
Press ? for help. It lists the global keys plus whatever the screen you are on adds of its own.
When things go wrong

It tells you, instead of freezing

It opens even when it cannot connect

A bad or expired certificate does not print an error and exit. The cockpit opens, shows exactly what failed, and tells you to run zipline auth enroll.

Reconnecting is visible

If the stream drops, the header shows how stale the numbers are. A dashboard that has quietly stopped updating looks identical to a healthy one, so it never does that.

Colour is optional

Set NO_COLOR and every state is still readable: health is carried by glyphs as well as colour, so nothing is lost on a monochrome terminal.

It needs 72 by 20

Below that it says so plainly rather than rendering a broken layout. It uses the alternate screen buffer, so your scrollback is untouched when you quit.

Not to be confused with

ziplined run --tui

That flag belongs to the runtime daemon, not the operator CLI. It shows one process monitoring itself and sends its logs to zipline-ziplined.log. The cockpit described here connects to the control plane and covers every pipeline and every instance at once.

CLI guide Full reference Try the CLI in your browser