block/goose

Choose this fork only if you specifically want a customized, frozen Goose distribution and are prepared to carry maintenance. If you want current agent capabilities or broad platform support, upstream is the safer choice.

Prefer this fork only if you want to build on its scheduler/orchestration and packaging changes. If you want a current, low-maintenance Goose deployment, upstream is the better choice.

Choose this fork only if its existing customizations match your target distro and you are prepared to maintain a large, outdated divergence. If you mainly want Goose itself, upstream is the safer choice.

Choose this fork if you want a heavily customized Goose variant with workflow and packaging changes and you are prepared to own long-term merge and maintenance cost. Do not choose it if you need close upstream compatibility or want the latest upstream behavior with minimal drift.

Choose this fork if you want a customized Goose distribution with provider/onboarding tweaks and you are comfortable losing some upstream integrations. Avoid it if you need broad upstream compatibility, especially extensions and older migration paths.

Choose this fork only if its custom provider and deployment changes matter more than staying current with upstream. If you want the broadest feature set and lower maintenance risk, upstream is the safer choice.

Choose this fork only if you want a customized Goose derivative and are prepared to own divergence. Stay with upstream if you want the broadest feature set, lower maintenance burden, and fewer surprises.

Prefer upstream unless you specifically need this frozen snapshot or want a clean base for your own fork. This fork adds no visible capabilities and is materially behind current goose.

Choose this fork if your priority is a local-first Goose distribution around Ollama. Choose upstream if you want the newest provider support, UI polish, and the broadest feature set with less maintenance risk.