Git-managed scoped agent memory

Agent memory becomes opaque, over-broad, or difficult to correct.

Source snapshot imported 2026-10-20. This is not a live feed. Source and contributions.

Workflow guide

Agent memory becomes opaque, over-broad, or difficult to correct.

Store atomic facts in explicit persona, shared, and workspace scopes with on-demand recall and Git review.

Evidence: public-synthetic-reproduction. Recorded: 2026-09-01.

Facts need to survive sessions while keeping scope, corrections and sources visible.

  1. Separate facts from tasks and decisions.
  2. Give each fact its source, scope and correction history.
  3. Retrieve only the scope needed for the current question.
  4. Test expected recall and forbidden cross-scope recall with synthetic facts.

Check your result

Current facts are retrieved, superseded facts are identified, and forbidden scopes stay out of the response.

Limits

  • Git history alone does not establish truth or authorization

Scoped-context tests · Memory desk

Original source