MEMTRACEMemDB

TEMPORAL GRAPH MEMORY

See how the code got here.Replay the path behind it.

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

Less guessing around every change.

01REPLAY

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.

02HISTORY

Ask what changed in the window that matters.

Trace the evolution of a file or symbol across a day, a sprint, or the period around an incident.

03CONTINUITY

Give the next agent the history the last chat lost.

Working-tree saves and Git commits remain queryable after the original coding session ends.

HOW MEMDB THINKS

The graph records what was true.Time records when it was true.

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.

TECHNICAL MODELLIVE
WORKING TREEA source save becomes a working_tree episode.
GIT HISTORYA commit becomes a permanent git_commit episode.
TIME MODELSymbols and relationships carry their valid time.
REPLAYEach episode can show its graph-level effect.
WITHOUT MEMDBRebuild the past from diffs and stale chat context.
WITH MEMDBReplay the exact save or commit with its graph effect attached.

BUILT INTO THE WORK

Record the change once, then query it days or months later.

  1. 01
    RECORD

    Capture the repository as it changes.

    The watcher records source saves while Git history provides the committed timeline.

  2. 02
    CONNECT

    Keep history tied to code structure.

    Changed symbols, calls, imports, and types stay connected to the episode that changed them.

  3. 03
    RECALL

    Query the moment you need.

    Agents can inspect evolution, replay one episode, or compare graph state across time.

MEMORY THAT SURVIVES THE SESSION

Stop asking the codebase to explain itself from scratch.

Keep the change history close enough for every developer and agent to use while the next decision is being made.