Skip to main content
Smithers has two terminal UI surfaces:
  1. bunx smithers-orchestrator init asks one interactive question (your preferred coding agent) unless you pass --yes / --non-interactive.
  2. bunx smithers-orchestrator up --interactive and bunx smithers-orchestrator workflow run --interactive open the run launcher and then the full-screen monitor.
The old standalone bunx smithers-orchestrator tui command was removed in 0.20.2. The current TUI path is the --interactive mode on run commands.

​
Interactive setup

Run init in a human terminal. It shows which coding agents it detected, asks which one you prefer, installs the workflow pack with defaults plus that agent’s plugin (or skill if no plugin exists), and then opens a hijacked tutorial session hosted by that agent:
Pass --agent claude (or codex, pi, …) to skip the question, and --no-tutorial to skip the guided session. For CI, scripts, or agent-driven setup, use the non-interactive form:

​
Interactive run launcher

Use up --interactive when you want Smithers to help pick a workflow and collect inputs:
From an interactive TTY, omitting the workflow argument also opens the same launcher:
Terminal screenshot of bunx smithers-orchestrator up --interactive showing the workflow picker

Captured from tmux: up --interactive opens a searchable workflow picker before it starts a run.

Use workflow run --interactive when you prefer workflow IDs over file paths:
Passing a workflow ID skips the picker and goes straight to the input prompts for that workflow:
Terminal screenshot of the interactive workflow input prompt

Passing an installed workflow id preselects it and prompts for its input schema.

​
Full-screen monitor

After the launcher starts the run, Smithers detaches the workflow process and hands your terminal to the full-screen monitor from @smithers-orchestrator/tui. The monitor connects to the workspace Gateway, starts one if needed, and streams the run tree, output, logs, diffs, timeline, and hijack state.
Terminal screenshot of the full-screen Smithers TUI monitor showing a finished run

After a run finishes, the monitor still shows its run tree and selected node details.

Useful keys: There is no silent fallback. If the TUI package cannot be resolved, the command fails with TUI_MONITOR_UNAVAILABLE while the detached run keeps running. Watch it with bunx smithers-orchestrator ps, bunx smithers-orchestrator inspect RUN_ID, or the run log file.

​
Command map

Agents should suggest the interactive commands to humans, but should not run them through an automation harness. If an agent is executing a workflow itself, use -d, --format json, ps, logs, inspect, and events instead.