Goose — Open AI Agent for Desktop, CLI, and API

Practical Notes

• Quant: the README claims support for 15+ providers plus 70+ MCP extensions via the open protocol.
• Quant: Goose now lives under the Agentic AI Foundation at the Linux Foundation, which matters for governance and project continuity.

Rollout pattern

• Use the CLI first even if you plan to adopt the desktop app, because CLI validation is easier to script and document.
• Test one provider path and one MCP extension path separately before you blend them in the same workflow.
• Record whether your team needs the desktop app, the CLI, or the API, because each surface implies different support obligations.

Watchouts

The repo is in a transition from block/goose to aaif-goose/goose, so older links and instructions may still exist in the ecosystem; pin current URLs in internal docs.

FAQ

Q: Is Goose only a CLI? A: No. The README describes a native desktop app, a full CLI, and an embeddable API.

Q: Why does the foundation move matter? A: It changes project governance and signals a broader community stewardship model.

Q: What should I validate first? A: Install the CLI, finish one task, and confirm at least one MCP extension works with your chosen provider.