FAQ
Short answers for questions people ask before and after a first run. For a printed error, start at [Find your message](index.md).
Short answers for questions people ask before and after a first run. For a printed error, start at Find your message.
Does the factory push or merge?
No. A successful run delivers a local commit on the factory branch in your repo, plus SUMMARY.md. Merging and pushing are yours. See What needs your approval and Multi-repo runs.
Does my code leave my machine?
Kusaw runs on your machine and starts no cloud agents. What an agent step sends to the model provider is the same kind of session as when you run that CLI yourself. Telemetry stays off until you turn it on. See What stays local and what doesn't and Telemetry.
Which agent CLIs can steps use?
Built-in agent steps call the Claude Code you already configured. Kusaw does not ask for credentials or pick a vendor plan. Other agent CLIs are not a second default in this version. See Install.
Can I replace a built-in step?
Yes. Every step, built-in or custom, is a program that speaks the same step protocol, so the built-in steps are defaults. Point the pipeline at your command: instead of builtin: and keep the same step id. See Replace a built-in step.
Can I run two tasks at once?
One factory runs one run at a time. Further tasks wait in that factory's queue as queued and start when nothing is active. Separate factories each have their own queue and can run at the same time. See Factories.
Can I use several repos in one task?
Yes. Name them in the spec (repos:) and scope verification commands under ### repo: <label> headings. At most eight repositories in one run. See Multi-repo runs.
How do I stop everything?
kusaw stop --all stops every running or finalizing run in that factory and pauses the queue. kusaw stop --all --all-factories does the same for every registered factory. To stop one run, kusaw stop <run>. The usage line the CLI prints if the arguments are wrong is Use kusaw stop <run> or kusaw stop --all.
Where are my logs?
The run page in the Dashboard shows live activity and logs. On disk, each attempt keeps stdout.jsonl and stderr.log under <data_dir>/runs/<run>/attempts/<stage>-<step>-<n>/. kusaw status prints the queue, the active run, and runs that need you. See Read the Dashboard.
How do I uninstall?
Stop serve, then kusaw forget <name> to drop the registry entry. That leaves the factory folder and data directory in place so you can delete them yourself. Remove the kusaw binary from PATH. See Factories.
What does needs_attention mean?
The run finished without succeeding and is waiting for you. After a loop hits max_iterations, the reason is loop_exhausted. You can requeue with a note, dismiss it, or take it over. See needs_attention after the loop limit.
How do I start the factory?
Run kusaw serve so the queue moves, then kusaw ui --open for the Dashboard. kusaw status shows whether the monitor is up. See Install and Your first run.
How do I approve a waiting gate?
When a run is waiting_for_human, kusaw status prints Waiting for you: and the gate name. Inspect the summary, diff, and verification output, then kusaw approve <run> (optional note) or reject with a note. Approval delivers a local commit; it does not merge. See Review and approve a run and A gate is waiting.
Does telemetry send my code?
No. Telemetry is off until kusaw telemetry on, and this version's metadata level does not send task text, logs, diffs, or paths. See Telemetry.