Search for a command to run...
Articles tagged with #goose-local-edition
The goose swarm, self-verifying: small local models shipping real software Key takeaways "It runs" and "tests pass" are not "it is correct." Every win was confirmed by executing the app on the spec's
Inside goose-swarm: How We Turned One Local Model Into a Self-Verifying Fleet Key takeaways The concurrency core is decoupled from any LLM by three traits, so the whole scheduler is unit-testable aga
Key takeaways swarm-gym is a Python harness (python -m harness ...) that drives goose local-edition's coding swarm, then grades what it built by RUNNING it, not by trusting the model. Two modes: benc
Key takeaways The swarm engine went from just under 7,000 lines to 21,191, and from 18 tunable levers to 100. Zero levers were removed. Every GOOSE_SWARM_* environment lever was silently OFF for the
goose compaction: my 27B re-read the file 95% of the time — quoting it in the summary didn't help Somewhere past turn 40, the worker that owns the integration pass in our swarm stops making progress a
goose swarm: pytest | head -80 exits 0 when nothing ran, and pipefail only trades the lie Key takeaways pytest exits 4 for a missing file, 5 for zero collected and 1 for a real failure. Piped through
