Hi, I’m Vivek Gupta, Founder & CEO at MemCode. GitAgent treats identity, rules, memory, tools, and skills as version-controlled agent assets, which creates an interesting opportunity to complement repo-local state with durable user and project memory.
Would GitAgent consider an optional MemCode integration? MemCode could hold scoped runtime memory—preferences, task outcomes, and learned context—while Git remains the source of truth for versioned agent configuration and team-shared rules.
I’d be glad to prepare a small example or PR around the appropriate storage or runtime hook. The integration can remain opt-in with clear scope and forget/delete behavior. Would a discussion or RFC be useful for exploring the boundary between git-native state and runtime memory?
Hi, I’m Vivek Gupta, Founder & CEO at MemCode. GitAgent treats identity, rules, memory, tools, and skills as version-controlled agent assets, which creates an interesting opportunity to complement repo-local state with durable user and project memory.
Would GitAgent consider an optional MemCode integration? MemCode could hold scoped runtime memory—preferences, task outcomes, and learned context—while Git remains the source of truth for versioned agent configuration and team-shared rules.
I’d be glad to prepare a small example or PR around the appropriate storage or runtime hook. The integration can remain opt-in with clear scope and forget/delete behavior. Would a discussion or RFC be useful for exploring the boundary between git-native state and runtime memory?