Inspeximus

inspeximus — the agent memory that takes it back

**Your agent's most expensive failure is not forgetting. It is confidently remembering the old answer.**

Long-term memory for AI agents in one zero-dependency Python file, plus an MCP server for any client and a one-line config install for Claude Code, Cursor, Windsurf, Codex and Cline.

Correcting a fact is not the hard part, and this field already does it. Graphiti invalidates facts and leads with it; cognee ships `forget` as one of its four operations. When we measured mem0 and Graphiti, both kept the corrected value, which is the right thing to do. What neither has is a channel to undo that correction on command, from an instruction that names no value. Here a fact that was wrong, or true on Monday and outdated by Friday, gets corrected once, and you can still put it back afterwards.

The benchmarks ask which of two conflicting facts wins. The question after that one is whether you can take the correction back, and whether you can show what changed.

The name is from medieval charters. A king, bishop, abbot or town council opened with *inspeximus*, "we have inspected", reciting an older document in full to record that they had examined it, usually confirming it, and sealing the result so a later reader could check. It attested that the copy faithfully matched the original, not that the original was true. Same guarantee here, and `provenance()` says so in a `limits` field rather than leaving you to find out.

[](https://pypi.org/project/inspeximus/) [](https://pypistats.org/packages/inspeximus) [](https://github.com/DanceNitra/inspeximus/actions/workflows/ci.yml) [](https://github.com/DanceNitra/ins