Installing bext-tui

bext-tui is a single static binary in the bext workspace. There are no system dependencies beyond a working terminal.

From source

bext-tui lives in crates/bext-tui inside the bext monorepo. Build it with cargo:

cd /path/to/bext
cargo build --release -p bext-tui

The binary is then at target/release/bext-tui. Copy it to a directory on your PATH:

sudo cp target/release/bext-tui /usr/local/bin/
bext-tui --version

Requirements


Rust	1.85+ (the bext workspace pins a nightly toolchain — `bext-tui` itself only needs stable but inherits the workspace's `.cargo/config.toml`)
Terminal	any terminal that supports a 256-color palette and the alternate screen — `xterm`, `iTerm2`, `WezTerm`, `Alacritty`, `kitty`, modern GNOME Terminal, modern Konsole. No support for the legacy Linux framebuffer console.
Locale	UTF-8 locale (status icons use Unicode block characters)

What it installs

A single statically-linked binary, ~10–14 MB stripped. No daemon, no config files needed for the default remote mode.

Verifying

bext-tui --help

You should see the CLI usage. To verify it can connect to a running bext instance:

bext-tui --host 127.0.0.1 --port 4000 --token "$BEXT_ADMIN_TOKEN"

Press q to quit.

Where the binary connects

By default bext-tui polls these admin API endpoints under your bext instance:

- GET /__bext/admin/api/overview

- GET /__bext/admin/api/requests

- GET /__bext/admin/api/cache

- GET /__bext/admin/api/workers

- GET /__bext/admin/api/proxy

- GET /__bext/admin/api/waf

- GET /__bext/admin/api/sites (falls back to /apps)

- GET /__bext/admin/api/certs

- GET /__bext/admin/api/deployments

- GET /__bext/admin/api/license

- GET /__bext/admin/api/config

- WS /__bext/admin/ws/logs for the live request stream

The bearer token must have admin access. For tenant-scoped tokens, the TUI will only see data for the tenant the token belongs to — that's enforced server-side.

Troubleshooting

broken pipe (os error 32) — your SSH session was killed without a clean shutdown. Re-launch the TUI; nothing is persisted server-side.

failed to enable raw mode — the terminal isn't a TTY. bext-tui needs an interactive terminal — it can't be piped or run inside non-PTY CI.

The screen is full of escape sequences — the panic hook didn't restore the terminal cleanly. Run reset or tput reset to clean it up.

certificate verify failed — bext-tui accepts self-signed certs in remote mode by default. If you're seeing this, rebuild with the workspace toolchain to make sure the rustls roots are up to date.