/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

block/goose

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:33:25.413Z

1mo ago

block/goose

block/goose is an actively maintained Rust-based open source AI agent for local engineering automation. It is large and mature, with a CLI, desktop app, documentation site, container tooling, and recent commits landing on March 30, 2026. For fork evaluation, it looks most interesting if you want to customize an autonomous agent stack rather than a thin code-assist tool.

Loading tags...

Stars33,757

Forks3,151

Default branchmain

Last pushed2026-03-30T15:22:25Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if its scheduler, recipe, or packaging choices are specifically what you need. If you want current Goose capabilities and lower maintenance risk, upstream is the safer choice.

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.

Fork comparison

jackjackbits/goose

38/100

stale

significant_divergence

Prefer this fork only if its scheduler, recipe, or packaging choices are specifically what you need. If you want current Goose capabilities and lower maintenance risk, upstream is the safer choice.

Likely purpose

A customized Goose distribution or experimental branch that keeps its own release/workflow choices, including scheduler and recipe handling changes, while diverging substantially from upstream’s newer provider, UI, and platform work.

Best for

Teams maintaining a custom Goose distro or internal fork; Users who prefer a fixed behavior set over upstream freshness; Developers willing to own integration work across CLI, UI, provider, and data changes

Additional features

Temporal scheduler support
Recipe URL encoding/decoding handling
Claude 4 model listing
Hermit/node-based project setup updates
Interactive mode spinner behavior fixes
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.

Missing features

Upstream’s newer provider and model work, including recent OpenAI streaming-tool JSON parsing and copilot-acp provider support
Recent UI/TUI and i18n fixes landed upstream after this fork’s last push
Likely loss or lag in bundled data/assets such as canonical model metadata and dictation token data
Material upstream progress since July 2025, so adopters should expect merge pain and stale behavior in newer Goose workflows
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Can be useful if you need the fork’s specific scheduler and recipe-related behavior
May fit teams that want a frozen, customized Goose baseline instead of fast upstream churn
The fork is large enough to indicate real product work rather than a trivial patch set

Risks

Very large two-way divergence makes rebasing or backporting expensive
The fork was last pushed in 2025-07, while upstream was active on 2026-03-30
Potential feature loss from large deletions in model and dictation data
New upstream fixes and providers are unlikely to be present without manual porting