levelrail-cli tui is a k9s-style terminal UI for operators who live in the shell. It shows the same data as the dashboard, refreshes on its own, tails logs, and can restart, deploy, roll back, stop and start an app, always behind a typed-name confirmation.
--team / --project scope as every other command, and only the public HTTP API, so a token with read access is enough to browse. It needs a real terminal: in a script or pipe it exits with an error and points you at apps list and attention instead.
Views
The header shows the profile, server host and version, mesh health (
mesh:healthy/peers, or off), and the incident and attention counts. Status colours follow the dashboard tones: green is healthy, red is failing or critical, yellow needs a look, grey is neutral or stopped, cyan is in progress.
Key map
In the logs view:
j/k scroll, g/G jump to top and bottom, f toggles follow, c clears the buffer. Lines are coloured by level (error red, warn yellow, info cyan, debug grey).
Command bar
Press: then one of the following. The app name is optional when an app is selected.
Confirmation and read-only mode
Every action that changes state asks you to type the app name before it runs. A mismatch changes nothing, andesc cancels. --read-only removes the action keys and the mutating commands entirely and shows a [READ-ONLY] banner in the header.
Secrets, environment values and tokens are never fetched or shown in the TUI. To reveal a value, use the dashboard.
Options
Apps, deployments and alerts refresh every interval with one batched list call each. Databases, nodes, domains, backups, mesh and the server version refresh every fifth interval. A request that is still running is never started twice, and a section that fails keeps its last data and shows the error when it has nothing else to show.