Memory backend for coding agents

Checkpoint, resume, branch, and inspect agent context without losing the plot.

ContextGraph preserves durable working state when coding agents hit compaction pressure. It stores decisions, open tasks, failures, changed files, and restoration instructions, then makes that state visible inside the repo through .contextgraph/.

  • Reactive delta compaction
  • Branch-aware context cache
  • Repo-local .contextgraph/
ContextGraph launch artwork
Built for compaction-safe coding workflows Self-hosted, inspectable, GitHub-native

Why now

Most agent memory still breaks exactly when work gets complicated.

Raw vector memory is not working state

Searchable text is useful, but it does not preserve the live decisions, blockers, and changed files that an agent needs after compaction.

One summary is too lossy

Compressing an entire session into one paragraph hides what is still open, what failed, and what should not be changed.

ContextGraph keeps durable state visible

It checkpoints structured session state, reuses branch prefixes cheaply, and writes the latest state into the repo so both humans and agents can inspect it.

Core features

A sharper alternative to “summarize and hope.”

Reactive Delta Compaction

Record decisions, constraints, tasks, failures, files, and artifacts as structured events, then emit deterministic delta packs when context gets tight.

Branch-Aware Context Cache

Fork from a checkpoint and reuse the shared reduced prefix so child branches recompute only their new work instead of rebuilding the whole session state.

.contextgraph/ Memory Directory

Materialize the latest session into readable repo-local files like resume_prompt.md, open_tasks.md, and failures.md.

Real-world use case

A coding agent is refactoring a payment service and the context window is collapsing.

The agent records durable events during the session: “keep the public REST API stable”, “do not break SDK compatibility”, “resume-path regression is failing”, “add migration tests”, and the files that changed.

When compaction hits, ContextGraph checkpoints that state instead of rewriting the whole chat. If the work branches, the new session reuses the inherited prefix. If another agent takes over tomorrow, it can reopen the repo and inspect .contextgraph/ immediately.

What survives compaction

  • Confirmed decisions
  • Active constraints
  • Open tasks and blockers
  • Changed files
  • Restoration prompt and instructions

How it works

One memory layer for agent continuity.

01

Track structured session events

Record decisions, tasks, failures, commands, artifacts, and file changes as durable state.

02

Checkpoint when context pressure hits

Emit a delta pack instead of rewriting the whole conversation into one fragile summary.

03

Reuse shared branch prefixes

Fork sessions from checkpoints and recompute only the branch-specific delta.

04

Inspect the repo-local memory

Open .contextgraph/ to review the latest prompt, failures, open work, and cache state.

Proof

See the product story in one screen.

Governed memory demo

Governed memory

Store, review, and recall memory with provenance, visibility, and policy intact.

ContextGraph dashboard demo

Operator visibility

Inspect trust, memory state, and shared knowledge through a dashboard built for teams.

Try it

Use the quickstart if you want the fastest proof. Open the README if you want the full story.