/monitor, so it works with no .smithers/ pack installed and no UI code written. It is pure observation: opening it launches no run, no workflow, and no agents.
10-second quickstart
bunx smithers-orchestrator ui does (explicit --gateway probe, then runtime-state discovery, then the legacy port probe on --port, default 7331) and autostarts smithers gateway when none is running. Disable autostart with --no-autostart; --no-daemon or SMITHERS_NO_DAEMON=1 disables daemonized autostart. It then opens the gateway’s /monitor page in the browser, deep-linking ?runId= when you passed a run id, and prints a { opened, url, gateway, runId } envelope.
What you see
- Workspace operations view: a paginated all-runs landing page with search and filters, grouped run states, an operations summary, scheduled crons, and a Metrics view.
- Run health and controls: an always-on health diagnosis with one-click recovery where available, plus Pause, Resume, Cancel, approvals, and run-level Scores.
- Execution history: the live expandable tree or XML view, a chronological Timeline, and a frame scrubber for inspecting earlier committed states.
- Node investigation: live output, recorded output and tool calls, an AI “what happened” recap, scorer results, syntax-aware diffs, and an embedded PTY terminal for hijacking or reopening supported agent sessions.
- Events and navigation: a filterable live event log with follow mode; shareable
?runId=/&nodeId=deep links; and?embed=1for the focused embeddable run surface. - Connection truth: distinct Live, Connecting, Offline, and Unauthorized states with state-specific recovery guidance.
How it relates to the other surfaces
The monitor replaced the retired
monitor workflow, which had to launch a durable run of agents just to look at another run. The command observes directly through the gateway instead.