Block's Goose: The Open-Source AI Agent That's Quietly Reshaping Local Development

When Block (formerly Square) released Goose as open source in September 2025, most of the developer press treated it as just another AI coding assistant. A year later, that framing looks wrong: Goose is one of the few agents that doesn't try to replace your editor — it tries to replace the shell.

What Goose actually does

Goose is a local-first AI agent built on the Model Context Protocol (MCP). Unlike Cursor or Copilot, which sit inside your IDE and suggest code, Goose runs as a CLI process on your machine. You give it a goal in natural language, and it executes: reads files, runs shell commands, edits code, calls APIs, and iterates until the task is done.

The architecture has three pieces:

1. A conversation layer (your terminal) where you describe what you want.
2. An LLM backend (any model with an OpenAI-compatible API — local or remote).
3. MCP extensions that let it touch the outside world: GitHub, your IDE, your database, your filesystem.

According to Angie Jones's talk at All Things Open 2025, Goose ships with connections to 1,700+ MCP servers, and the community has been adding more. This is the part that makes it different from a chat wrapper: it doesn't just suggest commands, it runs them in a loop and reads the output.

Why it matters

The local-first design has three practical consequences that don't show up in feature comparisons:

1. Privacy by default. Your code never leaves the machine unless you explicitly route the LLM to a remote provider. For developers working under NDAs, on proprietary codebases, or in regulated industries, this is the actual reason to pick Goose over Cursor.

2. Model-agnostic. Point Goose at Ollama, oMLX, LM Studio, vLLM, or any cloud API. A popular thread on r/LocalLLaMA walks through setting $OPENAI_HOST to point Goose at a local llama.cpp server. The same agent that uses GPT-4o on Monday can run on Qwen 2.5 32B locally on Tuesday.

3. Workflow-level automation. Because Goose can call shell and edit files, it isn't limited to "write a function." It can refactor a module, run the test suite, fix what broke, commit, and open a PR — all in one prompt. This is closer to what Devin or Claude Code promise, except Goose is open source, local, and the user keeps the keys.

Where it falls short

Goose is not a polished consumer product. The CLI experience is functional but minimal; the JetBrains and VS Code integrations exist but are not on par with what Cursor ships. The model quality ceiling is whatever you plug in — running a 7B local model will produce noticeably worse multi-step plans than GPT-4o.

For a single developer doing isolated tasks, a managed tool is faster. Goose's strength is the user who has already decided that local + open + scriptable is the right shape, and wants an agent that respects that.

Adoption signals

Since the September 2025 public release, Goose has accumulated 18,000+ GitHub stars and a Discord community in the thousands. The project ships releases on a roughly monthly cadence. Block is using it internally across its payments and Cash App engineering teams, which is the kind of dogfooding that tends to keep a project honest.

Why this is a story worth following

The interesting question isn't "is Goose better than Cursor." It's whether the local-first, model-agnostic, MCP-native pattern becomes the default shape of AI tooling over the next two years. If MCP continues to win as the integration standard — and Anthropic, OpenAI, and Google have all signaled support — then agents like Goose are the early examples of what every tool will eventually look like.

For now, Goose is the most credible open-source answer to "I want a coding agent that doesn't phone home." That's a narrow niche, but it's a real one.

---