5 Key Reasons Why Block Gifted Goose to the Linux Foundation

When internal tools take flight as public services, the tech world pays attention. Amazon did it with AWS; Block, the fintech powerhouse, did it with Goose. Originally built for Block's own developers, Goose—an AI coding agent—was released under a permissive license. But true open-source stardom required more. To address governance, trademark, and enterprise adoption hurdles, Block handed Goose to the Linux Foundation via the newly formed Agentic AI Foundation (AAIF). Here are the five pivotal reasons behind this strategic move.

1. The Rise of Goose as an Internal Tool

Goose began as an internal productivity booster at Block, designed to streamline coding tasks for over 12,000 employees. Within two months of deployment, it gained rapid adoption, proving its value as an AI agent that could handle complex development workflows. Its success inside Block hinted at broader potential, much like how AWS evolved from Amazon's internal needs. The tool's effectiveness laid the groundwork for its open-source release, but the transition from internal utility to external service demanded careful stewardship.

2. Early Success and Adoption Challenges

After Goose went public, it attracted quick uptake from the developer community. However, Manik Surtani, former head of open-source at Block and now CTO of AAIF, revealed to The New Stack that this early success came with “headwinds.” The primary obstacle was a lack of transparency in project governance. Without clear oversight, enterprises hesitated to commit. The tool was open-source in code but not in spirit—Block still controlled its trademarks, creating a trust barrier that limited enterprise adoption. Without change, Goose's potential would remain grounded.

3. Governance Gaps and Trademark Issues

The core problem was that Goose wasn’t entirely free and open. Block retained ownership of its trademarks, which hampered enterprise adoption. Companies feared vendor lock-in or sudden shifts in project direction. Surtani emphasized that true open-source governance required independent oversight. Block realized that to let Goose “unfurl its wings and soar,” the project needed a neutral home. Transferring trademarks and governance to a foundation would signal stability and encourage broader contributions from the community and corporate sponsors alike.

4. Choosing the Right Foundation Home

Block explored several foundations before settling on the Linux Foundation. After discussions with the MCP (Model Context Protocol) team, the Goose Crew, and experts at Anthropic, it became clear that a dedicated entity was needed. The solution: co-found the Agentic AI Foundation (AAIF) as an arm of the Linux Foundation. This choice offered instant credibility, established governance practices, and a vendor-neutral environment. Block could focus on technology while the foundation handled legal and community growth. The move also aligned with the Linux Foundation's experience in hosting multi-stakeholder AI projects.

5. The Agentic AI Foundation and Its Trio of Tools

The AAIF launched with three core tools: Goose, MCP, and Agents.MD. Surtani noted this bundle was partly for expediency—to get the foundation operational quickly. But it also created a synergistic ecosystem: MCP standardizes model-context interactions, Agents.MD documents best practices, and Goose provides the execution engine. The foundation is open to more projects, aiming to become a hub for agentic AI development. By handing Goose over, Block ensured its code, community, and future would thrive under shared governance, not corporate whims.

In handing Goose to the Linux Foundation, Block demonstrated a mature approach to open source: recognizing when a project outgrows its creator and needs an independent, community-driven structure. The Agentic AI Foundation now guides Goose and its companion tools toward enterprise-ready transparency, while Block continues as a contributor. For developers and corporations alike, this move signals that agentic AI is ready to fly—not under a single company's wing, but as a collaborative fleet.