CLI reference
Commands for the published alpha.6 workflow runtime.
Use bunx laufwerk@0.0.1-alpha.6 as the command prefix. Run project commands from the consumer root, the directory containing laufwerk/.
Setup and discovery
| Command | Purpose |
|---|---|
--version | Identify the installed CLI release |
--help | List supported commands |
init | Initialize a new project with hello and authoring skills |
init --example coding | Also add the complete coding workflow |
init --update-skills | Refresh managed skills in an existing consumer |
doctor | Inspect local credentials, tools, identity and package versions |
doctor --provider claude --refresh | Attempt Claude subscription renewal if needed |
workflows | List workflow definitions |
init refuses to overwrite an existing Laufwerk project. Run it once. Missing consumer dependencies can be reinstalled with bun install --cwd laufwerk.
Execute and inspect
bunx laufwerk@0.0.1-alpha.6 run WORKFLOW --input '{"executionKey":"NEW_KEY"}'
bunx laufwerk@0.0.1-alpha.6 status
bunx laufwerk@0.0.1-alpha.6 status RUN_ID --watch
bunx laufwerk@0.0.1-alpha.6 timings RUN_ID --json
bunx laufwerk@0.0.1-alpha.6 studioThe input must match the selected workflow; executionKey is the coding starter's field, not a universal required field. status lists up to 50 recent runs. --json on supported observation commands is intended for scripts; JSON watch emits changed snapshots.
Timings can overlap and are not a substitute for total elapsed time. Token usage is shown when reported by the provider, not guaranteed for every run.
Interactions and control
bunx laufwerk@0.0.1-alpha.6 respond RUN_ID INTERACTION_ID --response '{"kind":"confirmation","value":true}'
bunx laufwerk@0.0.1-alpha.6 approve RUN_ID INTERACTION_ID
bunx laufwerk@0.0.1-alpha.6 approve RUN_ID INTERACTION_ID --deny --reason 'Not appropriate for this task'
bunx laufwerk@0.0.1-alpha.6 resume RUN_ID
bunx laufwerk@0.0.1-alpha.6 cancel RUN_IDrespond answers workflow human requests. approve answers agent tool approvals. Human decisions explains the difference.
recover requires an operation result or error and a reason; use it only after resolving uncertainty. See recovery guidance.
Result semantics
A successful command is not always a completed workflow. waiting means something still needs an answer. completed means the workflow finished, while its business result can still say declined. Do not treat an accepted asynchronous request as proof of publication.