Troubleshooting

Symptom	What to do
“the repository has uncommitted changes”	Commit or stash first. Runs always start from a clean HEAD.
A gate is skipped: “tool not installed”	Install the project’s dependencies in your repository (npm install), and keep node_modules in dependencyDirs.
“model server unavailable”	Check the server is running and baseUrl ends in /v1. curl <baseUrl>/models should list a model.
Tasks blocked with “plan too large for context”	Use a model with a larger context, or ask for a smaller change.
Many “edit search text not found”	The model is not copying code exactly. A larger or less quantized model usually helps.
The planner keeps asking	Answer with harness answer RUN_ID (or in the app); the run continues.
A run stopped (crash, Ctrl+C, power)	harness resume RUN_ID continues from the last saved step.
Windows: paths too long	Keep the harness folder short (for example C:\harness); worktrees live under it.