Portable agent memory
A shared memory layer for coding agents.
The simple version: Codex and Claude sessions become Markdown notes in Obsidian. qmd indexes those notes so agents can search prior work before starting from zero.
The team version: everyone contributes to one shared vault, then each laptop builds its own fast local index over the same institutional memory.
One machine: from chat to memory
This is the local loop on a single laptop. The important point is that the memory is ordinary Markdown, so humans can inspect it and agents can retrieve it.
Agents write raw session logs
While you work, Codex and Claude already leave session history on disk. These files are useful, but too noisy to be the memory layer directly.
~/.codex/sessions~/.claude/projectsA sync step converts them into clean notes
The exporter keeps the visible user and assistant conversation, adds metadata, groups sessions by project, and drops the bulky tool noise.
sync_codex_sessions.shObsidian becomes the memory store
The vault separates raw conversation memory from more durable team knowledge. Sessions are recoverable; notes are curated.
sessions/<project>clean exported chats
notes/<topic>reports, decisions, guides
qmd builds the searchable index
The agent does not trawl the whole vault manually. It asks qmd for relevant notes, then reads the actual Markdown behind the results.
qmd searchqmd vsearchqmd queryFuture agents retrieve before they act
You can ask, "check our recent chats about this", and the agent can pull prior sessions, notes, and reports into the current task.
notes/Team mode: one shared vault, many local indexes
The team version keeps the same simple primitives. Every engineer writes Markdown into the shared vault, and every engineer reads the same vault through their own local qmd index.
Engineers work locally
One vault accumulates memory
sessions/what the team discussed and triednotes/the distilled decisions, reports, and guidesEveryone reads the latest context
qmd update and qmd embedqmd index can stay local. That keeps the first version simple while still giving every engineer access to the same institutional context.The extra value: intent behind the code
Normally the durable record is just the diff: what changed in the code. With shared agent memory, the team can also recover why it changed, what options were considered, what constraints mattered, and which conversations led to the decision.
Nightly Dream Mode: reconcile the sources of truth
Once the team is using a shared vault, the overnight pass becomes the quality layer. It checks what changed during the day and prepares source-backed updates so tomorrow's agents start from the latest truth.
What the dream pass reads
It should look beyond the vault, because not all institutional knowledge starts in notes.
qmd update and qmd embed so the next day's agents retrieve the cleaned memory.