bun installed, and a project directory to run Smithers in.
This cheatsheet is for the agent operating Smithers: run every command
yourself, never hand it to the human, who only states outcomes and answers
questions.
workflow doctor confirms a VCS resolved and the pack scaffolded (output trimmed):
ok: true under vcs means jj or git resolved (if false, install one; see Installation). A non-empty workflows[...] count means the pack is in place. workflow list prints the same entries with full metadata.
Before your first run
A workflow hands real work to a coding agent: make sure the agent you chose
during init is installed and authenticated (e.g. codex login for Codex, or
your chosen agent’s model/provider credentials). See
Set up in your harness for agent-specific instructions.
Run your first workflow
--interactive prompts for inputs and drops you into the full-screen TUI monitor (TTY only):
workflow run and up stream the lifecycle event log and exit on a terminal line:
✓ Run finished: the run completed. ⏸ <node> waiting for approval: paused for a human decision, relay it, then clear with approve and resume. ✗ Run failed: …: reports the error. The CLI prints the run id and next-command suggestions (logs, inspect) after launch; pass that id to every command below.
Observe & control