cindyxu1030/agent-memory-vault — explained in plain English
Analysis updated 2026-05-18
Give Claude Code, Codex, and Cursor a shared memory that survives across sessions.
Keep per project decisions and facts separate from global rules.
Review agent generated feedback before it becomes a permanent rule.
Point an existing coding project at the vault so agents write memory back into it.
| cindyxu1030/agent-memory-vault | 123satyajeet123/bitnet-server | ahloiscreamo/pod-search | |
|---|---|---|---|
| Stars | 0 | 0 | 0 |
| Language | Shell | Shell | Shell |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 2/5 | 2/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Agent Memory Vault is a ready made Obsidian vault template that gives AI coding assistants like Claude Code, Codex, and Cursor a shared, lasting memory. Normally each agent session starts from nothing, and each tool keeps its own separate memory, so what one assistant learns about you and your projects never reaches another. This template solves that by turning one folder of plain markdown files into a shared brain that every agent reads rules from and writes memory back into. The vault is organized into a handful of folders. A rules folder holds things you want agents to remember forever, such as your voice and cross cutting principles, and only you can edit it directly. A projects folder holds one subfolder per project, each containing the project's own memory of decisions and facts plus a feedback folder that tracks corrections. A sources folder holds clipped articles and references, and a maps folder holds visual diagrams. A feedback folder contains a graduation queue, where patterns seen across multiple projects wait for a human to approve them before they become permanent global rules. To get started, you create your own copy of the template repository, rename the folder to whatever you want your vault called, and open it in Obsidian. You then fill in placeholder text describing yourself in a rules file, rename the example project folder to your first real project, and run an included script that checks for accidentally exposed secrets, broken links, and other problems before you commit anything. Every agent session is expected to read the rules and the active project's memory on startup, and to write feedback and updated memory back into the vault as it works. The project also documents optional weekly and nightly maintenance routines for vaults with heavier use.
An Obsidian vault template that gives Claude Code, Codex, and Cursor a shared, persistent memory stored as markdown files.
Mainly Shell. The stack also includes Shell, Obsidian, Markdown.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.