Proposal: durable project and user memory for Goose sessions

Hi, I’m Vivek Gupta, Founder & CEO at [MemCode](https://memcode.in). Goose is designed for extensible, tool-using agent workflows, and its users build up useful project context, preferences, and decisions over many sessions.

Would Goose consider an optional MemCode memory integration? MemCode provides durable, scoped memory that can preserve project conventions, user preferences, tool decisions, and learned context across sessions and model changes, while leaving the existing local and self-hosted paths intact.

I’d be glad to prepare a small example or PR around the appropriate extension point. The integration can be opt-in, with explicit scopes, retrieval controls, and forget/delete behavior. Is there a preferred design discussion or contribution path for this?