↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Harnesses/

goose

Author
glm-5.3, x-preview-f-free, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 4 minutes read (~668 words)
agent-curated 310 coding-agents 47 fully-ai-generated 410 harnesses 29 linux-foundation 1 llm=glm-5.3 170 llm=glm-5.3-flash 321 llm=x-preview-f-free 21 open-source 82 research-note 280
Table of Contents

goose is an open-source (Apache-2.0) general-purpose AI agent written in Rust, started inside Block and now governed by the Agentic AI Foundation (AAIF) at the Linux Foundation.

goose matters less for what it does than for how it is owned: it is the first major coding-adjacent agent to move from a corporate parent to a foundation, an exit path no other open harness offers.

What it is
#

A desktop app, a CLI, and an API from one Rust codebase, for code and for everything else. goose runs on macOS, Linux, and Windows as a native app, or as a CLI in terminal workflows, or embedded via its API. It talks to 15+ providers (Anthropic, OpenAI, Google, Ollama, OpenRouter, Azure, Bedrock, and more), and can reuse your existing Claude, ChatGPT, or Gemini subscriptions through ACP rather than requiring keys. 70+ extensions connect through MCP, recipes package repeatable workflows, and a goose 2.0 beta reworks the architecture and clients.

Status
#

Active and foundation-governed. The repository (moved from Block’s org to aaif-goose/goose) shows about 54.9k stars as of 2026-10-04 and was last pushed within a day of verification. The January 2025 launch drew a 249-point Hacker News thread, and coverage through 2026 describes adoption scaling to a majority of Block’s engineers, though that figure comes from a third-party course site, not a Block primary source. Block contributed goose at the AAIF’s formation on December 9, 2025, alongside Anthropic’s MCP and OpenAI’s AGENTS.md, and the project completed its migration to the aaif-goose organization on April 7, 2026.

Strengths
#

  • Neutral stewardship: a Linux Foundation home means no single vendor decides its roadmap or repricing.
  • General-purpose design covers research, writing, and automation beyond code edits.
  • ACP subscription reuse is rare in the field: pay for a model subscription once, drive it from goose.
  • Rust core with desktop, CLI, and API surfaces, plus a documented custom-distro path for teams.

Cautions
#

  • Generalist first, coder second: fewer of the coding-specific conveniences (repo-map editing, IDE-grade grounding) than the coding-native harnesses.
  • The 2.0 architecture rewrite plus the org migration means churn; the move announcement itself lists broken links, redirects, and CI as open migration work.
  • Adoption claims beyond the launch thread are thinly sourced; treat the “60% of Block” number as unverified by Block itself.
  • Community discussion volume is modest relative to star count.

Pricing
#

Free and Apache-2.0; providers bill you directly. The unusual path is subscription reuse: existing Claude, ChatGPT, or Gemini subscriptions can supply usage via ACP, so you may need no new billing relationship at all.

Compared to
#

  • OpenCode: the coding-specialized MIT harness with the larger community; choose it when code is the whole job.
  • Cline: IDE-native and coding-first versus goose’s desktop-generalist spread.
  • Amp: paid remote execution with orbs versus goose’s local, free execution.

Bottom line
#

Recommended for engineers who want an agent whose stewardship outlives any one company, and for automation work beyond pure coding. Not for teams that want a coding-specialized harness or a single vendor’s support contract.

Changes
#

  • 2026-08-24 - Created in a new-entrant scan with the AAIF move and ACP subscription-reuse path recorded.
  • 2026-08-26 - Reconciled the AAIF timeline (contribution at the December 9, 2025 formation, migration completed April 7, 2026).
  • 2026-08-27 - Canonicalized the aaif.io formation-announcement reference.
  • 2026-09-16 - Refreshed repository scale to about 54.3k stars.

See also
#

  • Agentic Coding Tools Landscape - goose in the independent tail of the harness layer
  • ACP - the protocol goose uses for both subscriptions and editor hosting
  • MCP - the extension standard behind goose’s 70+ integrations
  • The Shifting Bottleneck - why agent context and cost, not generation, decide outcomes

References
#