FAQ
Short answers for questions people ask before and after a first run.
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 and anonymous usage reports stay off until you turn them 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 by default. Cursor is an optional second provider that you enable per machine and pick per step. Kusaw does not ask for credentials or pick a plan. Any other CLI can run as a custom step. See Providers.
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?
Yes. A factory runs up to worker.max_parallel runs at once (default 3, at most 8). Further tasks wait in that factory's queue as queued and start when a slot frees up. Separate factories each have their own queue and run side by side. 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-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 runs, and runs that need you. The logs of kusaw serve, kusaw ui, and kusaw up are under <user config dir>/kusaw/logs (~/.config/kusaw/logs on Linux). kusaw logs serve -f follows the serve log. See Read the Dashboard and kusaw logs.
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 and the ksw alias from PATH (make uninstall does this if you used make install). Service logs and the registry are under <user config dir>/kusaw/. 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 it (with an optional note), dismiss it, or take it over. See needs_attention after the loop limit.
How do I start the factory?
Run kusaw up --open (serve and ui together). 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 its metadata level does not send task text, logs, diffs, or paths. Separate anonymous usage reports are also off until you opt in. See kusaw reporting and What stays local and what doesn't. See Telemetry.