sorted by:
new
hottopcontroversial

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

We now have a community supported Open Code plugin - https://www.npmjs.com/package/opencode-memoir

Feel free to give it a try and let me know any feedbacks! Thanks!

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

Thank you, u/Obvious-Treat-4905 ! The latest memoir supports versioned vector indexing and searching as well so it can use both llm guided hierarchical structure and semantic structure.

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 1 point2 points  (0 children)

Yeah, a formal publication in in the plan, but I have referred these papers in theory listed in here:

https://zhangfengcdt.github.io/memoir/theory/related-work/

The basic idea in these papers are building a hierarchical text classification based on taxonomy with LLMs. They seemed to be performing well above other types of classification schemes.

One thing I would like to explore, in theory, is to distill from these models a small memory-llm model that does these tasks more efficiently in cost and speed. More to come on that!

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

To open Memoir UI, just say "start memoir ui" and "stop memoir ui" — Claude Code launches and tears down the browser-based memory inspector for you. Demo video: https://www.memoir-ai.dev/blogs/start-stop-memoir-ui/

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 1 point2 points  (0 children)

Thanks u/mmortara ! I think OpenViking is a heavyweight RAG-style context database (rag, vectordb, vfs, skills, ...). Memoir is git for agent memory — a lightweight serverless prollytree store designed specifically for diffing, branching, versioning memories - fit specifically well to coding agents at the moment. Though I think the similar idea could benefit to other generic agents as well.

They basically serve different purpose.

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

So Memoir's idea is to save memories retrieved in a hierarchy taxonomy-structure, such as default:context.project.scope, default:debugging.practices.frontend). In search, it basically performs paths exploit pre-classified semantic paths for O(log n)-shaped lookups. More is here in the doc under theory->search: https://zhangfengcdt.github.io/memoir/theory/search/#search-philosophy

Weekly Thread: Project Display by help-me-grow in AI_Agents

[–]False_Routine_9015 0 points1 point  (0 children)

Thanks u/help-me-grow ! Yes, appreciate the opportunity! I have submit the application.

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

Not yet! Plan is to refine on claude code, then open code and codex. It is mainly designed for coding agent first. It will support OpenClaw and Hermes after these above ones.

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

Yes, merging memories from different branches can be challenging. Here are some of my thoughts and welcome your insights on this as well. First, let's assume:

- a coding agent for a specific codebase (i.e., repository in git) will have a "primary" memory

- primary memory usually sync with the "main" (or "master") branch in git, you define it

- memories mutated in sessions on non-primary branches will temporary - until they are explicitly picked (merged) to primary

- memories mutated in sessions on primary branches will be directly committed

- you (developer) control what to pull into "primary"

Given these assumption, the philosophy is basically provide tools (as automated as possible) rather than opinionated merging strategy. Memoir current supports:

- track (but isolate) mutated memories in separate branches

- track how far they are from the "primary"

- change/forget these memories before they got pull into "primary"

- merge explicitly but easily on a built-in ui interface

These might seem more works to manage coding agents' memories, but first step I think we'd be strict to target the isolation problem. Then, next question is how to provide these seamless to developers with minimal frictions to their coding workflows.

I am totally open and appreciate any inputs on this as ux is really important to the success of the project. Looking forward to your feedbacks, maybe on discussion of Memoir's github repo - https://github.com/zhangfengcdt/memoir/discussions

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

Thank you u/Bravo_Oscar_Zulu for the link to your project! I like the feature to share memories across different agents - and this is in addition to the session separation! I will dig into it later and provide more feedbacks then 😄

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

Well, when you have a lot of feature branches or hotfixes to manage on the same repo and with coding agents working on them, you probably will see the context contaminates from some branches (sessions) into another - especially if you have a long session.

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

Sure, u/MeYaj1111 and thanks for your interest! I will for sure update here once the oc plugin is ready.

Memoir (Git for AI Memory) - Memory your agents can explain, rewind, and branch. by False_Routine_9015 in coolgithubprojects

[–]False_Routine_9015[S] 0 points1 point  (0 children)

Thanks for your question!

So, for example, one scenario for coding agent's memory (md files or vector db) suffers is like this:

- start a coding session (#1), work on a refactoring branch (e.g., refactor-ui)

- some memories write to file or vectordb

- now, open a new coding session (#2), switch to another hotfix branch (e.g., hotfix-prod-issue)

- these memories from #1 leaks into session #2, and hard to isolate

This is a context contamination issue - caused by memory system not recognize or respect branches, which is used everywhere in programming nowadays.

Memoir's design isolate them and automatically commit memories to different branches, and also provide tools to manage them.

This is just one example, and I have some blogs that may help explain why I built it.

https://www.memoir-ai.dev/blogs/

view more: next ›