Review draws on 5 primary sources (vendor announcements, named publications, benchmark results) and is updated continuously as the product changes. See the methodology page for the full research process.
TL;DR: Goose is the open-source extensible AI agent originally built by Block (Square’s parent). On April 7, 2026, Block donated Goose to the Linux Foundation’s Agentic AI Foundation (AAIF) — alongside Anthropic’s Model Context Protocol (MCP) and OpenAI’s AGENTS.md standard. The repo is now at github.com/aaif-goose/goose with ~29K stars and Apache 2.0 license. Native desktop apps for macOS/Linux/Windows plus a CLI. Connects to 25+ LLM providers (Anthropic, OpenAI, Google, Ollama, Mistral, Grok, Azure, Bedrock, OpenRouter). 70+ documented MCP extensions, 3,000+ available across the ecosystem. Free; you bring the model. Best for developers who want a fully vendor-neutral, locally-run agent platform.
What Goose is in 2026
Goose started as Block’s internal AI agent project. Block (the company behind Square, Cash App, and TBD) open-sourced it in early 2025 under Apache 2.0. By 2026, ~29,000 GitHub stars and a real community. On April 7, 2026, Block donated the project to the Agentic AI Foundation (AAIF) at the Linux Foundation — a new umbrella initiative that consolidates open-source agentic AI standards.
Why the AAIF donation matters: AAIF now owns three foundational agentic-AI assets:
- MCP (Model Context Protocol) — Anthropic’s standard for agent tool calling, donated to AAIF
- AGENTS.md — OpenAI’s repo-level agent configuration spec, donated to AAIF
- Goose — Block’s open-source agent runtime, donated to AAIF
This is a genuine consolidation moment for open-source agentic AI. For developers banking on vendor-neutral agent infrastructure, AAIF is now the credible long-term home for the standards.
What Goose actually does
Goose is a local agent runtime. Not a model — you bring the model. Not a SaaS product — you run it on your machine.
Core capabilities:
- Native desktop apps for macOS, Linux, Windows — graphical chat interface for non-terminal users
- Full CLI for terminal-first workflows (similar to Claude Code’s TUI)
- 25+ LLM providers: Anthropic (Claude Opus 4.7, Sonnet 4.6, Haiku), OpenAI (GPT-5.5, GPT-5), Google (Gemini 3.1 Pro, Flash), local via Ollama (Llama, DeepSeek, Qwen 3 base), Mistral, xAI Grok, Azure, AWS Bedrock, OpenRouter, Together, DeepInfra
- MCP-native — Goose was one of the first agents to ship MCP support; the entire extension ecosystem (3,000+ tools across the MCP catalog) is available
- Lead-worker model architecture — different models for different agent roles (planning model + execution model + code-review model). Cost-optimization pattern that single-model agents can’t match
- Scheduled tasks — run agents on a timer (cron-like scheduling for autonomous workflows)
goose serve— run Goose as a background service for integration with other tools- Gemini OAuth + Copilot ACP — first-class authentication for Google and GitHub model providers
- Security features — egress logging inspector (log all outbound network calls), restricted secrets file permissions, audit trails
Goose isn’t trying to be the prettiest agent. It’s trying to be the most extensible one.
Pricing
Goose itself: $0. Apache 2.0 licensed. No paid tier. No “Pro” version. Costs come from the model you pair it with:
- Free with local Ollama models: $0 marginal cost. Llama 4 70B, DeepSeek V3 distill, Qwen 3 32B all work
- Cheap with DeepSeek V4 Flash: ~$0.28/M output tokens. Heavy daily use rarely exceeds $5/month
- Standard with Claude Sonnet 4.6: ~$5–20/month moderate use
- Frontier with Claude Opus 4.7 or GPT-5.5: $50–150/month for heavy power users
The lead-worker model architecture makes cost optimization easier than single-model agents — use cheap models for planning and code review, expensive models only for hard execution.
What Goose does well
Vendor independence at the model layer. Same as Aider — you control which model runs your work. But Goose adds a richer extension ecosystem and a real desktop app on top.
Linux Foundation governance. Now under AAIF alongside MCP and AGENTS.md. For organizations that need vendor-neutral standards (regulated industries, governments, large enterprises with procurement-skeptical legal teams), this is real.
Lead-worker architecture. Routing different agent steps to different models is a 2026-frontier feature. Most commercial agents use one model end-to-end. Goose lets you use Opus 4.7 for planning, Sonnet 4.6 for execution, Haiku for code review — meaningfully cheaper at scale without quality loss.
Native desktop apps. Unlike Aider (CLI only) or Claude Code (terminal-only), Goose ships GUI apps. For non-terminal-comfortable users this lowers the barrier to OSS agent adoption.
MCP-native. Goose was an early MCP adopter; the extension ecosystem is mature. Plug in 3,000+ pre-built MCP tools (databases, APIs, file systems, cloud providers).
Strong security posture. Egress logging, restricted secrets permissions, audit trails — security-first design that matters for regulated industries.
Scheduled tasks built in. goose schedule (or equivalent) lets you run agents on cron schedules. Useful for “every morning at 9, summarize the project status” workflows.
$0 baseline cost. Free + local Ollama = $0 marginal cost agent platform. For OSS contributors and budget-constrained developers, this is genuine accessibility.
Where Goose falls short
UX polish lags Claude Code. The native apps work but feel less refined than commercial tools. The CLI is functional, not delightful.
Configuration overhead is real. Setting up Goose with the right model providers, MCP extensions, and lead-worker routing takes a few hours of fiddling. Claude Code is claude and you’re done.
Less mindshare in the developer community. Most “AI coding tutorials” target Claude Code or Cursor first. Goose’s documentation is thorough but the Stack Overflow / Reddit knowledge base is thinner.
Newer to the AAIF home. The April 7 donation is recent. The transition from Block’s GitHub to aaif-goose/goose is still settling — issue queues, contributor processes, release cadence all moving under new governance.
Quality bottleneck is the model you pair. Goose isn’t doing ML research; quality scales with whichever LLM you connect. The agent runtime is great; you still need a competitive model.
Less polished on Windows. macOS and Linux desktop apps are first-class; Windows tracks but feels secondary.
Goose vs the alternatives
For polish and integrated UX: Claude Code > Goose. Real gap on UX refinement.
For vendor independence: Goose ≈ Aider. Both are vendor-neutral; Goose has GUI apps + richer extension ecosystem; Aider is CLI-first with stronger git integration.
For free coding agent in terminal: Gemini CLI > Goose for accessibility (1,000 free Gemini requests/day with Google account). Goose more capable but requires bringing your own model.
For organizations needing governance: Goose > everything else. AAIF stewardship is the strongest open-governance story shipping.
For lead-worker / multi-model routing: Goose > all alternatives. Unique architecture.
For absolute coding quality: Tied to whichever model you pair. Goose + Opus 4.7 ≈ Claude Code with Opus.
For non-terminal users wanting OSS agent: Goose > Aider. Native desktop app is real differentiator.
Full ranking at best AI coding tools in 2026.
Who should use Goose
- Developers wanting a vendor-neutral, free, GUI-or-CLI agent platform
- Organizations needing Linux-Foundation-governed open-source agent infrastructure
- Power users running multi-model lead-worker workflows for cost optimization
- OSS contributors wanting to extend an agent platform via MCP
- Self-hosters running Llama / DeepSeek / Qwen locally via Ollama
- Security-conscious teams needing egress logging and audit controls
- Anyone tired of “the model lab also owns the agent UI” lock-in
Who shouldn’t
- Polished-UX seekers — Claude Code is meaningfully more refined
- Simple “one tool, one bill” users — Claude Pro or Cursor Pro is simpler
- Casual / occasional coders — overkill; Gemini CLI free tier is friendlier
- Windows-first organizations — macOS / Linux are better-supported
The verdict
Goose in April 2026 is the most strategically important open-source AI coding tool shipping. The AAIF donation alongside MCP and AGENTS.md makes it the infrastructure layer for vendor-neutral agentic AI — not just another agent product, but the governance home for the standards everyone is building on.
The pragmatic read: Goose is the right pick if you value the open-source-foundation governance story. For pure productivity, Claude Code is more polished. For pure vendor neutrality, Aider is simpler. Goose’s edge is being both open and feature-rich, with Linux Foundation backing.
The 2026 open-source agent landscape now has a clear shape:
- Goose (Apache 2.0, AAIF-governed, GUI + CLI, multi-provider) — the institutional pick
- Aider (Apache 2.0, single-developer-led, CLI-only) — the personal pick
- Gemini CLI (Apache 2.0, Google-led, CLI, generous free tier) — the easy onramp
All three are credible. All three matter. Goose’s bet is that institutional governance produces better long-term outcomes than vendor-led products — and the AAIF donation suggests Block is committed to that bet.
For OSS-aligned developers, Goose is now the safest long-term choice in the category.
Related:
Goose — frequently asked questions
What does Goose do?
Goose started as Block's internal AI agent project. Block (the company behind Square, Cash App, and TBD) open-sourced it in early 2025 under Apache 2.0. By 2026, ~29,000 GitHub stars and a real community. On April 7, 2026, Block donated the project to the Agentic AI Foundation (AAIF) at the Linux Foundation — a new umbrella initiative that consolidates open-source agentic AI standards. Why the AAIF donation matters: AAIF now owns three foundational agentic-AI assets: 1. MCP…
How much does Goose cost?
Goose itself: $0. Apache 2.0 licensed. No paid tier. No "Pro" version. Costs come from the model you pair it with: - Free with local Ollama models: $0 marginal cost. Llama 4 70B, DeepSeek V3 distill, Qwen 3 32B all work Cheap with DeepSeek V4 Flash: ~$0.28/M output tokens. Heavy daily use rarely exceeds $5/month Standard with Claude Sonnet 4.6: ~$5–20/month moderate use Frontier with Claude Opus 4.7 or GPT-5.5: $50–150/month for heavy power users
What are the downsides of Goose?
UX polish lags Claude Code. The native apps work but feel less refined than commercial tools. The CLI is functional, not delightful. Configuration overhead is real. Setting up Goose with the right model providers, MCP extensions, and lead-worker routing takes a few hours of fiddling. Claude Code is `claude` and you're done.
What are the best alternatives to Goose?
For polish and integrated UX: Claude Code > Goose. Real gap on UX refinement. For vendor independence: Goose ≈ Aider. Both are vendor-neutral; Goose has GUI apps + richer extension ecosystem; Aider is CLI-first with stronger git integration.
Who should use Goose?
Developers wanting a vendor-neutral, free, GUI-or-CLI agent platform Organizations needing Linux-Foundation-governed open-source agent infrastructure Power users running multi-model lead-worker workflows for cost optimization OSS contributors wanting to extend an agent platform via MCP Self-hosters running Llama / DeepSeek / Qwen locally via Ollama Security-conscious teams needing egress logging and audit controls Anyone tired of "the model lab also owns the agent UI" lock-in
Is Goose worth it in 2026?
Goose in April 2026 is the most strategically important open-source AI coding tool shipping. The AAIF donation alongside MCP and AGENTS.md makes it the infrastructure layer for vendor-neutral agentic AI — not just another agent product, but the governance home for the standards everyone is building on. The pragmatic read: Goose is the right pick if you value the open-source-foundation governance story. For pure productivity, Claude Code is more polished. For pure vendor neut…
Featured In
Thinking about trying Goose?
The button below goes to Goose's official site. Signing up through it may earn this site a small commission at no cost to the reader. That helps keep Pick Right running and is never the reason a tool gets recommended.
Learn More →