Goose memory: hints for the project, nothing for the history
Goose is explicitly context-engineering aware: hints files, instructions, extensions. Context you can engineer by hand is still context you have to maintain by hand.
Block. Sources checked 2026-09-25.
How Goose handles memory today
Goose documents goosehints: global hints in the config directory and project hints in .goosehints, plus AGENTS.md and similar instruction files. Hints are read into sessions to reduce repeated prompting.
Goose also documents a memory MCP extension pattern, which is the supported way to attach a persistent store rather than keeping everything in hint files.
What Goose forgets
Hints describe the project. Memory should describe the work.
- Conversation history between sessions, so yesterday’s conclusions are not available today.
- Hint file growth, which turns instructions into an archive that costs tokens on every run.
- Cross-tool continuity with editors and CLIs you also use.
- Reasoning detail that you never distilled into a hint.
The fix with MemoryRouter
Add MemoryRouter as a Goose extension over MCP and the agent gets recall and store tools backed by a vault shared with your other tools.
- 1
Add the remote MCP server to Goose
Register the MemoryRouter endpoint as an extension, then authenticate through the OAuth flow. Remote streamable HTTP is supported.
Goose extension config
{ "mcpServers": { "memoryrouter": { "url": "https://mcp.memoryrouter.ai/mcp" } } } - 2
Trim the hints that became history
Move dated decisions out of .goosehints and into memory. Hints should say how to work; memory should say what happened.
Connect Goose over MCP and share the vault with your editors and CLIs. 14-day free trial.
Related
Goose memory FAQ
Sources
Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.