Repository navigation
Sample and provider path for user-scoped MemCode memory #8817
Description
Hello Agent Framework team. I’m Vivek Gupta, Founder & CEO of MemCode (memcode.in).
I’m looking for the right way to offer persistent, user-scoped context to agents built with the framework. A first contribution could be a focused Python sample that explicitly writes an approved fact and recalls it in a later workflow; it would keep token handling with the host application and would not use conversation history as an automatic write stream.
If a memory backend belongs in the framework’s provider surface, I’d also be interested in a first-class implementation, with matching behavior in .NET after the contract is agreed. Identity isolation, consent, bounded retrieval and fail-open reads would be the acceptance criteria.
Is there an existing interface or design issue I should use? I can prepare the smallest PR you would welcome. https://memcode.in/docs
cc Roger Barreto (@rogerbarreto) for your thoughts on this integration.
Activity
[-]Proposal: MemCode as an optional or core memory backend for Microsoft Agent Framework[/-][+].NET: Proposal: MemCode as an optional or core memory backend for Microsoft Agent Framework[/+][-].NET: Proposal: MemCode as an optional or core memory backend for Microsoft Agent Framework[/-][+]Python: Proposal: MemCode as an optional or core memory backend for Microsoft Agent Framework[/+][-]Python: Proposal: MemCode as an optional or core memory backend for Microsoft Agent Framework[/-][+]Sample and provider path for user-scoped MemCode memory[/+]eavanvalkenburg commentedon Oct 2, 2026
Thanks for the detailed proposal and for engaging with the framework! At this time we don't plan to add third-party memory backends like MemCode directly into Agent Framework's provider surface. We'd encourage hosting and releasing this as your own package using the existing
ContextProviderinterface — happy to see it discoverable in the community ecosystem. We're also working on ways to make external provider packages like this easier for users to find.