🚀 goose public roadmap: Feb - Mar 2025

[angiejones]

📅 Last Updated: February 24, 2025

codename goose is evolving rapidly! Below is our 6-week roadmap, outlining our top priorities across different workstreams. Plans may shift based on progress and feedback. Feel free to join discussions, share thoughts, or contribute!

🔹 Foundation Enhancements (Scoped Work)

Focusing on core capabilities to keep goose secure, reliable, and performant.

✅ Trust Progression for goose – Implement Permission Before Tool Call (PbTC) and user-configurable control modes to ensure transparent actions #1331

✅ Core Improvements

• Shared configuration storage for the app and CLI Unified Config #1286
• Streamlined developer experience for building and debugging MCP extensions
• Enhanced code quality through refactoring

✅ goosebench – A lightweight benchmark suite to verify goose’s functionality and performance, providing clear metrics to diagnose issues and optimize configurations. #1432

✅ UI Improvements

• Better path detection and selection when spawning a new session.
• Real-time feedback on remaining context window length.
• Navigation enhancements: revisit recent prompts and improved conversation switching.
• Config management in UI: View/edit config.yaml, integrate it into provider/extensions state management, and implement a Provider Registry UI.
• Improved input experience: Keep the input box active while goose is generating results.

project board for UI improvements

---

📈 Ecosystem Growth (Scoped Work)

Expanding goose's reach through integrations, features, and learning tools.

✅ In-App Learning – Self-paced, interactive tutorials in CLI and UI, including a goose Extensions Builder tutorial.

✅ Reusable, Sharable Sessions – Users can reopen and share sessions easily.

---

🧪 Experimental Work

Testing new ideas while maintaining platform integrity.

🔬 Tool-Calling Shims & Small-Model Experiments – Evaluating small models on consumer hardware, experimenting with tool-calling shims, and sharing findings via a community post.

🔬 Reasoner Experiments – Testing advanced decision-making with a reasoner plus operator combo, implemented as a goose extension #1300

🔬 Windows Support – Developing Windows versions of goose App & CLI, iterating through targeted testing.

📢 Got ideas? Share them in the comments! 👇

[thewildofficial]

elegant rate limits so that agent responses are (mostly) end-to-end for gemini users 🙏

[wendytang]

Estimated token usage so far

[ketzusaka]

I'd love a native app built for MacOS instead of the current webview based solution.

[angiejones]

updated roadmap to add UI Improvements under Foundation Enhancements section

[cliffhall]

Any chance of getting support for reusable MCP Prompts on the roadmap? Full MCP support would be great, but Prompts, in particular, is what I'm on about. For instance, how often, when using goose for development do you have to follow up the generation of some code with "Please also unit test, run lint, typecheck, etc."? I feel like those prompts need to be automated and I loathe the idea of building a solution for it when it's in the MCP already.

[kalvinnchau]

Hey @cliffhall we just got some preliminary support for MCP Prompts in the cli (currently in the canary) with a discussion going on at #1401. UI implementation further out pending some design thoughts on how to approach it.

[Tonksthebear]

Thank you for sharing the roadmap! Has there been any discussion on support for resource templates? It seems every other aspect of resources are supported but resource templates would be incredibly helpful https://modelcontextprotocol.io/docs/concepts/resources

[cliffhall]

Regarding resource templates, I found the need for them this weekend on a new MCP server called puzzlebox where I'm hosting state machines. It exposes tools for creating a state machine (a "puzzle") and for moving it through its various states, and for peeking in on its state.

But I want to subscribe to changes in a puzzle's state from a client perspective. So that two agents who care about the same puzzle will be made aware when one or the other of them changes its state.

I could not find an appropriate way to do that other than to expose it as a dynamic resource with a resource template like puzzlebox:/puzzle/{id}