Terminal UI

Run openloop with no arguments in a TTY and instead of help you get the full-screen terminal UI: a Solid.js/OpenTUI application covering the whole fleet.

Tabs

Keys 1–9 jump between tabs; Tab/Shift+Tab cycles; ? toggles the help overlay; q quits.

Key	Tab	What’s there
1	Dashboard	Fleet overview: daemon, budget, queues
2	Projects	Registry; activate, add, remove, init
3	Tasks	Ledger browser with status filters
4	Service	Start/stop/pause/resume the daemon
5	Config	Global & project settings editor
6	Run	Trigger and watch a run
7	Promotions	Queue; apply or reject
8	Events	Audit log with time/project filters
9	Logs	Daemon log and per-project run summaries

Keybindings within tabs

• Lists: ↑/↓ or j/k to move.
• Projects: Enter activate · a add · d remove · i init.
• Tasks: f filter status · a add · d delete · r recover stuck.
• Service: Enter execute the selected action.
• Config: Tab switch global/project · Enter edit · R reload.
• Run: Ctrl+R run.
• Promotions: Enter detail · a apply · r reject.
• Events: s cycle time window · p filter project.
• Logs: Tab daemon/project · Enter open file.
• Esc cancels dialogs / goes back.

TUI vs. CLI

The TUI is a viewer and light editor over the same state the CLI manages; nothing TUI-specific persists. Any action available in a tab has an exact CLI equivalent (see the CLI reference), which makes the TUI easy to drive from muscle memory in either direction. Outside a TTY (CI, scripts, pipes), openloop behaves as a normal CLI and prints help.