Hi @Nivesh353, I'm Vivek Gupta, Founder & CEO at MemCode.
GitAgent's memory/ directory gives agent context a history people can inspect, diff, and branch. A complementary use case is carrying a small set of approved user preferences or project decisions between separate agent repositories and machines.
A first contribution could expose MemCode save and recall through GitAgent's custom tools or plugin surface. Git would remain the source of the agent's versioned memory. Imported facts would be explicit and attributable, and nothing would synchronize the memory/ directory or create commits automatically.
Does an optional tool example fit your roadmap? I can put together a focused PR showing authentication, repository scoping, and graceful behavior when the remote service is unavailable.
MemCode documentation: https://memcode.in/docs
Vivek Gupta
Founder & CEO, MemCode
Hi @Nivesh353, I'm Vivek Gupta, Founder & CEO at MemCode.
GitAgent's memory/ directory gives agent context a history people can inspect, diff, and branch. A complementary use case is carrying a small set of approved user preferences or project decisions between separate agent repositories and machines.
A first contribution could expose MemCode save and recall through GitAgent's custom tools or plugin surface. Git would remain the source of the agent's versioned memory. Imported facts would be explicit and attributable, and nothing would synchronize the memory/ directory or create commits automatically.
Does an optional tool example fit your roadmap? I can put together a focused PR showing authentication, repository scoping, and graceful behavior when the remote service is unavailable.
MemCode documentation: https://memcode.in/docs
Vivek Gupta
Founder & CEO, MemCode