Menu
Render the workflow graph without executing it. Run `smithers graph --help` for usage details.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Drive Smithers, a durable control plane for long-running coding agents. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work: "orchestrate agents", "run a workflow", "implement this and review it", "keep iterating until tests pass", "plan then build", or anything that needs retries, approvals, replay, or evals across multiple AI steps. YOU (the agent) run Smithers on the user's behalf; it is not a GUI the human clicks. You are an ORCHESTRATOR: run long-running, multi-step, or background work *through* Smithers, not through your own ad-hoc subagents; spend your time observing the run and reporting.
Drive Smithers, a durable control plane for long-running coding agents. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work: "orchestrate agents", "run a workflow", "implement this and review it", "keep iterating until tests pass", "plan then build", or anything that needs retries, approvals, replay, or evals across multiple AI steps. YOU (the agent) run Smithers on the user's behalf; it is not a GUI the human clicks. You are an ORCHESTRATOR: run long-running, multi-step, or background work *through* Smithers, not through your own ad-hoc subagents; spend your time observing the run and reporting.
Query node/run lifecycle history by default; pass --raw for raw agent chunks and all event types. Run `smithers events --help` for usage details.
Output detailed run state. Structured output canonically uses nodes[].nodeId (legacy steps[].id remains for compatibility); --pool tallies attempt engine/model usage. Run `smithers inspect --help` for usage details.
Build a new Smithers workflow from a plain-English description. Dispatches to the create-workflow builder. Run `smithers init` first if the .smithers/ pack is not yet installed. Run `smithers make-workflow --help` for usage details.
Concise run health at a glance: verdict, node counts, agent/model mix, throughput, and the nodes gating progress. Run `smithers status --help` for usage details.
| name | smithers-graph |
| description | Render the workflow graph without executing it. Run `smithers graph --help` for usage details. |
| requires_bin | smithers |
| command | smithers graph |
Render the workflow graph without executing it.
| Name | Type | Required | Description |
|---|---|---|---|
workflow | string | yes | Workflow ID (from smithers workflow list) or path to a .tsx workflow file |
| Flag | Type | Default | Description |
|---|---|---|---|
--runId | string | graph | Run ID for context |
--input | string | Input data as JSON | |
--root | string | Tool sandbox root directory (same semantics as up) | |
--compact | boolean | false | Omit task prompt/text bodies (structure only) — validate that a workflow compiles without flooding output with every prompt |
