--- title: "Good Because There's No Vendor — Goose and the Fairness of Recipes" date: 2026-10-10 model: qwen3.6-plus author_type: human category: reviews summary: Block's Goose makes vendor neutrality, local-first, MCP extension, and recipe reuse its weapons. The Linux Foundation handoff cut the lock-in risk, but model-quality transfer, extension setup friction, and churn over "there are better tools" are recorded alongside it. tags: Goose,MCP,Block,Linux Foundation,vendor neutral,recipe,user reviews,real user reviews,AI agent --- # Good Because There's No Vendor — Goose and the Fairness of Recipes A question on r/LocalLLaMA: "Anyone using Block's Goose? On social media, apart from Block employees, I don't see it much. How does it compare to Aider, Claude Code, and gemini-cli?" First reply's opening sentence: "I like it. **It's not a purpose-specialized coder — it's an MCP client with an AI-utility metaphor.**" Second reply, a churn after two months: "It was useful, but there are better tools now." Third reply, left after using it to run MCP servers: "The servers..." (the thread cuts off before the reason). This post evaluates Goose on a single axis — **vendor neutrality** — and sorts out where that axis flexes and where it buckles. --- ### 1. What Goose actually sells **MCP extension.** Goose's core is less a code harness than an MCP host. You attach standard MCP servers and extend the tool ecosystem. **Recipes.** If a session is a "conversation," a recipe is a "repeatable procedure" — a parameterized stored prompt plus config. One real-use account: "I turned tricky multi-step work into recipes and stopped re-explaining it every time. It's a mechanism that lets everyone on the team execute one engineer's clever workflow identically." **Vendor neutrality and local-first.** Attach it to a local runtime like Ollama and the core inference loop never touches an external API. A de facto option for air-gapped and regulated industries. **Governance.** The Linux Foundation handoff. The answer to "what happens when a vendor changes the terms of the deal" — an answer a single-vendor agent can't give. --- ### 2. What it pays for **Model quality transfer.** The review's core sentence: "Goose is only as good as the model running it. The house model doesn't make the agent shine. Face it with a weak model and you get a pretty weak agent with a CLI. That isn't Goose's fault — it's Goose's reality." **Extension setup friction.** "Extension discovery isn't as smooth as a curated app store. You have to read the README, hunt down the environment variables, and edit the config. I burned time on an extension that did nothing because the key was missing." **The polish gap.** "Output format, confirmation prompts, and inner-loop speed sit one step below the most polished commercial agents." The difference in investment scale shows up as something you can feel. **Early churn.** The "used it two months, then moved to a better tool" churn reads less as missing features and more as a record that the model selection and setup cost ran higher than the community expected. --- ### 3. Where Goose wins The review's prescription is clear: **when neutrality is a constraint rather than a preference.** - Regulated industries, strict data-handling rules - Having been burned by a price or license changing under your feet - Workloads that must stay entirely in-house - Workflows the whole team has to execute the same way (recipes) Conversely, if all you want tonight is an excellent agent in your terminal and you don't care about lock-in, a single vendor's co-tuned tool is smoother on day one. --- ### 4. Conclusion — justifying neutrality The user record on Goose compresses into one sentence: **the harness is excellent, and the intelligence is left to the model.** MCP extension, recipes, and the Linux Foundation are Goose's proprietary stake. That stake has value in a market for a "safer choice" rather than a "better coder." Meanwhile the setup friction and polish gap are limits of investment scale that don't disappear overnight. The reason to pick Goose isn't the feature list — it's **governance and portability**. If that reason is what you need, Goose is the most defensible option among terminal agents so far. Related posts: [OpenCode user reviews](/reviews/2026-10-10-opencode-user-reviews/) · [browser-use user reviews](/reviews/2026-10-10-browser-use-user-reviews/) · [Goose agent hub entry](/agents/goose/) --- ### Sources - Community: [Anyone using Block's goose? (r/LocalLLaMA, 2025-10)](https://www.reddit.com/r/LocalLLaMA/comments/1lww2ld/) - Real-use review: [Goose CLI Review after Linux Foundation handoff (Pickuma, 2026-06)](https://pickuma.com/for-dev/goose-cli-review-block-open-source-agent/) - Official: [block/goose GitHub](https://github.com/block/goose)