Static web UI

Valved ships a minimal, static HTML UI — run history, per-run detail, logs, and pipelines — served locally. It’s deliberately simple: no live updates, no interactivity beyond links. It’s one client among many, not the primary surface (Valved is headless by default).

valved docs serve [--host H] [--port N] [--watch] [--no-auto-regen]
valved docs open

valved docs serve serves the UI on loopback and regenerates pages on run events. valved docs open opens it in your browser.

What’s in it

• Run history — recent runs with status and timing.
• Per-run detail — the run’s steps, structured logs, and outcome.
• Pipelines — the registered pipelines and their composition.

What it is not

• No live-updating dashboard — pages are static HTML, regenerated on events.
• No lineage view — data lineage is answered by valved ask today.
• No authoring — you build and deploy from the CLI, REST, or MCP.

Regenerating

valved docs regen                # regenerate all pages
valved docs regen --page runs    # regenerate one page

For anything richer — programmatic queries, dashboards, custom UIs — use the REST API, which carries the full surface with auth, streaming, and webhooks.