Hud module
Layer 5. Objects. Objects It is the HUD those records share.
shc hud opens x9s (k9s’s terminal UX) with the SHC provider baked
into this binary (cli/hud.go, pkg/x9sprov). It replaced the
bespoke bubbletea dashboard that lived at modules/hud.
That package, its daemon snapshot builder, and
GET /api/method/shc.hud.stream are deleted. The TUI dials the
same public HTTP API every other shc command uses. There is no
HUD-specific daemon route.
| CLI | shc hud |
| Provider | shc hud --x9s-serve (self-exec child) |
| HTTP endpoints | none of its own; reads and writes ride existing module routes |
| Views | stacks, events, apps, nodes, backups, tasks, audit, tenants, repos, workers, users, integrations, schedules, secrets, quotas, certificates, storage, volumes, config, connections |
HUD-local surfaces that had no x9s counterpart (the install wizard,
the client-log pane, the forwards panel) left with the old TUI.
shc install and shc forward remain as CLI verbs.
An untagged build (no -tags=x9shud) refuses with X501216HUDTUI.
See also
Section titled “See also”- CLI reference
- The HUD on a phone: the Console’s gestures and keyboard
- x9s provider
shc@docs:~$