Open the change, not a pile of diffs.
Replay one save or commit as a graph episode. See the symbols and relationships it added, changed, or removed.
TEMPORAL GRAPH MEMORY
MemDB keeps code structure and change history in one temporal graph. Your agent can inspect a save or commit, then compare the surrounding window without rebuilding the past from scattered files and logs.
File saves and commits stay attached to graph history
WHAT IT CHANGES
Replay one save or commit as a graph episode. See the symbols and relationships it added, changed, or removed.
Trace the evolution of a file or symbol across a day, a sprint, or the period around an incident.
Working-tree saves and Git commits remain queryable after the original coding session ends.
HOW MEMDB THINKS
MemDB is the temporal storage layer inside Memtrace. It keeps repository structure, relationships, and episodes together, so history can be queried as part of the code model instead of reconstructed later.
BUILT INTO THE WORK
The watcher records source saves while Git history provides the committed timeline.
Changed symbols, calls, imports, and types stay connected to the episode that changed them.
Agents can inspect evolution, replay one episode, or compare graph state across time.
MEMORY THAT SURVIVES THE SESSION
Keep the change history close enough for every developer and agent to use while the next decision is being made.