'hyve tui'
Why
The TUI was removed to shrink the core binary (it pulled in a full terminal-UI framework) and simplify the codebase. A standalone TUI project may be picked back up later as a separate initiative, but hyve’s core CLI doesn’t depend on it, and nothing about plain-flag usage changed — every command the TUI could drive was already, and still is, fully usable directly.
What to use instead
Every command documented in the CLI Reference works standalone via flags — nothing requires the TUI. If a guide elsewhere in these docs mentions running hyve tui as a shortcut, use the equivalent flag-based command shown alongside it instead.