---
title: "#goose-local-edition articles | Hashnode"
description: "Explore the latest #goose-local-edition articles, tutorials, and guides on Hashnode."
url: "https://hashnode.com/tag/goose-local-edition"
---

Tag

# #goose-local-edition

0 posts · 0 followers

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 19](https://hashnode.com/posts/the-goose-swarm-self-verifying-small-local-models-shipping-real-software/6aaeb0dbfd3d2cec51312076)

### [The goose swarm, self-verifying: small local models shipping real software](https://leanzero.hashnode.dev/the-goose-swarm-self-verifying-small-local-models-shipping-real-software?utm_source=hashnode&utm_medium=feed)

How we forked Block's goose into a multi-agent swarm running three small local models on LM Studio, with a gate stack that judges work by running it.

19 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/the-goose-swarm-self-verifying-small-local-models-shipping-real-software?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 19](https://hashnode.com/posts/inside-goose-swarm-how-we-turned-one-local-model-into-a-self-verifying-fleet/6aaeb09f8b4027f9f4df691c)

### [Inside goose-swarm: How We Turned One Local Model Into a Self-Verifying Fleet](https://leanzero.hashnode.dev/inside-goose-swarm-how-we-turned-one-local-model-into-a-self-verifying-fleet?utm_source=hashnode&utm_medium=feed)

How goose local edition works: the scheduler, the parallel planner, the CONTRACTS discipline, the model-free judge, and the smoke and AST gates.

24 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/inside-goose-swarm-how-we-turned-one-local-model-into-a-self-verifying-fleet?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 19](https://hashnode.com/posts/swarm-gym-for-goose-grading-local-models-by-running-the-code-they-write/6aae85c2c1dc87f3f56e2474)

### [swarm-gym for goose: grading local models by running the code they write](https://leanzero.hashnode.dev/swarm-gym-for-goose-grading-local-models-by-running-the-code-they-write?utm_source=hashnode&utm_medium=feed)

A hands-on swarm-gym tutorial: set up the goose local-edition swarm testbed, run both modes, read every output, and tune the swarm from what you find.

17 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/swarm-gym-for-goose-grading-local-models-by-running-the-code-they-write?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 19](https://hashnode.com/posts/making-the-goose-swarm-predictable-602-commits-100-levers-and-three-bugs-i-found-writing-this/6aae8567a22cecc64514d65c)

### [Making the goose swarm predictable: 602 commits, 100 levers, and three bugs I found writing this](https://leanzero.hashnode.dev/making-the-goose-swarm-predictable-602-commits-100-levers-and-three-bugs-i-found-writing-this?utm_source=hashnode&utm_medium=feed)

602 commits on goose local edition: what changed in the swarm, what the desktop looks like now, and three defects I found in my own honesty checks.

23 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/making-the-goose-swarm-predictable-602-commits-100-levers-and-three-bugs-i-found-writing-this?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 19](https://hashnode.com/posts/goose-compaction-my-27b-re-read-the-file-95-of-the-time-quoting-it-in-the-summary-didnt-help/6aae2f30e1223f8c1c85cc10)

### [goose compaction: my 27B re-read the file 95% of the time — quoting it in the summary didn't help](https://leanzero.hashnode.dev/goose-compaction-my-27b-re-read-the-file-95-of-the-time-quoting-it-in-the-summary-didnt-help?utm_source=hashnode&utm_medium=feed)

Compaction summarised away the tool output holding the file. Quoting the file into the summary left 18/20 re-reads; the last turns verbatim, 0/20.

18 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/goose-compaction-my-27b-re-read-the-file-95-of-the-time-quoting-it-in-the-summary-didnt-help?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 18](https://hashnode.com/posts/goose-swarm-pytest-head-80-exits-0-when-nothing-ran-and-pipefail-only-trades-the-lie/6aadaf0a4cccd7b4df060956)

### [goose swarm: pytest | head -80 exits 0 when nothing ran, and pipefail only trades the lie](https://leanzero.hashnode.dev/goose-swarm-pytest-head-80-exits-0-when-nothing-ran-and-pipefail-only-trades-the-lie?utm_source=hashnode&utm_medium=feed)

pytest exits 4 for a missing file; piped to head it exits 0 in bash and zsh. Why a goose swarm worker went green, and why pipefail is not the fix.

20 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/goose-swarm-pytest-head-80-exits-0-when-nothing-ran-and-pipefail-only-trades-the-lie?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 18](https://hashnode.com/posts/goose-local-edition-a-benchmark-that-runs-the-app-your-agent-built/6aad83a72021808a8feb0e51)

### [goose Local Edition: a benchmark that runs the app your agent built](https://leanzero.hashnode.dev/goose-local-edition-a-benchmark-that-runs-the-app-your-agent-built?utm_source=hashnode&utm_medium=feed)

Our goose fork, its swarm engine, and a scorer that boots the built app and prices what a user would get. On the current board our own fleet is last of 17.

25 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/goose-local-edition-a-benchmark-that-runs-the-app-your-agent-built?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 18](https://hashnode.com/posts/building-a-scorer-that-cant-flatter-itself/6aad835d5586e8ea3c515be1)

### [Building a scorer that can't flatter itself](https://leanzero.hashnode.dev/building-a-scorer-that-cant-flatter-itself?utm_source=hashnode&utm_medium=feed)

How we built an execution-graded benchmark for coding agents, and the six disciplines that caught every number it published wrong the first time.

38 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/building-a-scorer-that-cant-flatter-itself?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 18](https://hashnode.com/posts/openais-codex-spent-six-days-on-goose-and-never-completed-a-single-run/6aad5888e8b24ac425cc40ed)

### [OpenAI's Codex spent six days on goose and never completed a single run](https://leanzero.hashnode.dev/openais-codex-spent-six-days-on-goose-and-never-completed-a-single-run?utm_source=hashnode&utm_medium=feed)

Six days of OpenAI Codex on goose produced not one completed run. The same model in a different harness worked fine. Why the harness is the product.

9 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/openais-codex-spent-six-days-on-goose-and-never-completed-a-single-run?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Sep 18](https://hashnode.com/posts/goose-the-config-error-we-logged-432-times/6aad2dd0e4c060423a875126)

### [goose: the config error we logged 432 times](https://leanzero.hashnode.dev/goose-the-config-error-we-logged-432-times?utm_source=hashnode&utm_medium=feed)

A duplicate YAML key failed a whole config file. The loader warned 432 times into a log nobody reads, returned Ok, and the run used defaults.

8 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/goose-the-config-error-we-logged-432-times?utm_source=hashnode&utm_medium=feed)
