True Memory Fragments MCP server

True Memory Fragments

<!-- mcp-name: io.github.kyle641320/true-memory-fragments -->

Code changed, but your AI coding agent still remembers the old call chain? TMF is source-bound code memory that flags stale claims and points back to current source.

Try demo · MCP setup · Evidence

30-second paced replay of real deterministic demo output, with labeled source excerpts—not an agent end-to-end test. Reread is requested, not executed.

• Traceable code relationships: bind call, read, write, inheritance, and API claims to source fingerprints.
• Explicit stale results: omit stale claims and stop covered graph expansion instead of silently reusing old context.
• Targeted reread guidance: return source anchors so an agent can check the changed code.

Developer preview: enforcement depends on the host, configuration, and intercepted actions—not automatic blocking of all writes. Fresh does not mean correct; general token savings and production readiness are not established.

Who it is for

• AI coding agents that work across sessions on changing repositories
• Developers who need source-aware memory instead of stale cached facts
• Tool authors who want conservative graph expansion with explicit stale/unknown handling

Validated so far

• Source-bound freshness and stale-claim detection
• Hard stale gates that stop unsafe graph expansion
• Deterministic Python and Java validation
• Scoped agent experiments demonstrating stale-context prevention

TMF’s core stale-context protection mechanism has been validated in the covered scenarios. Evaluation across more languages, repositories, and long-running production workflows is ongoing.

What TMF is — and is not

TMF is for:

• AI coding agents working across sessions on changing codebases
• Preventing stale call-chain and dependency assumptions
• Source-bound code memory and conservative code-graph navigation
• Agent integrations that need an explicit stale/unknown result

TMF is not:

• A general chat-memory product or vector database
• A replacement for reading source code
• A guarantee that every claim is correct because it is fresh
• A proven general productivity or token-saving solution

Fresh means the source binding still matches. Correctness still comes from source and validation.

The repository includes a Java qualification suite: 46/46 qualifiers and 731/731 checks. The historical unreleased audit baseline was 478/478 tests; it is not the current test total. See the version-pinned test verification for historical rc3 and master results, explicit skips, and the intermittent master failure recorded at that time. The rc5 release notes distinguish the newer doctor implementation checks from release validation. These are source-analysis and regression-test results, not a claim of production readiness or a general Agent outcome. Middleware mechanics are validated, and stale-context safety has positive evidence in the GUAVA M10 pre-read experiment. Broader productivity, speed, token savings, and general bug-prevention claims remain unproven. See the authoritative evidence status before making broader claims.

Flow

Shortened. The full README is on GitHub.