Step 11 · Observability · Observability · Web cockpit, TUI, and doctor ENPT
Alembic Complete Visual Course

Web cockpit, TUI, and doctor

Observe and verify Alembic runs and environment without leaving the terminal or browser.

Read the plain version, or open the technical layer on any section.
1

See what is happening


@alembic/web serves a self-contained dashboard that lists runs, streams events.jsonl via SSE, and lets you approve parked T4 tasks. @alembic/tui draws the same information as ASCII swimlanes in the terminal.

alembic doctor probes the local environment: Node, pnpm, git, Higgsfield CLI, data directory, and the LLM gateway. It reports OK / WARN / FAIL for each check.

Think of it like… the flight deck of an airplane: instruments tell you speed, altitude, and warnings; you decide whether to continue.

Under the hood

The web cockpit polls append-only JSONL files and uses server-sent events for live updates. The TUI uses pure render functions so it is testable without a terminal. doctor uses which and version commands for binaries, fs.access for the data directory, and an HTTP probe for the gateway.

2

In one picture


alembic doctor Web cockpit TUI Run directory: index.json, events.jsonl, t4-parked.jsonl, approvals.jsonl Both cockpit and TUI read the same append-only journals
Doctor probes prerequisites; cockpit and TUI observe the same run directory.
3

In the code


# check environment
alembic doctor --json

# watch a run in the terminal
alembic tui <run-id>

# stream recent events
alembic tail <run-id> --follow

Implementation notes

alembic tail reads events.jsonl and prints swimlane-formatted lines. With --follow it polls every 500 ms. The TUI uses raw terminal mode so single keystrokes like q exit immediately.

4

Try it


Run a short Forge-scope command, then run alembic tui <run-id> and alembic tail <run-id> in separate terminals.

Compare: When would you prefer the TUI over the web cockpit?
5

Quick check


Which command reports environment health as JSON?