Skip to content

History / 20 Token Efficient Retrieval

Revisions

  • docs: refresh wiki for v12.6.0 and GitHub hosting

    Heinrich Krupp committed Nov 5, 2026
  • Drop a personal store size from the scan-limit note The page illustrated MCP_MAINTAIN_SCAN_LIMIT with "on a 17,000-memory store, a default run covers roughly the first eighth". That number described one particular store, not anything about the software, so it read like a benchmark it never was — and it was wrong twice over: it came from _count_existing_memory_rows(), a hash-embedding guard heuristic that sums the memories and memory_embeddings tables, so it double-counted. What matters is the rule, which holds at any size: the limit takes the first N in storage order, so repeated runs re-scan the same N and never reach the rest.

    Henry Krupp committed Aug 9, 2026
  • Add token-efficient retrieval guide; correct stale facts on Home memory_explore and memory_detail shipped in v11.1.0 with no user-facing documentation anywhere, which is how a user with 11k memories came to file a feature request for most of what they already do (#215). New page walks from the symptom — search responses eating 10k tokens — through limit and max_response_chars, then the two-phase map for people who want an overview before pulling content. It leads with the prerequisite, because memory_explore returns count=0 for every query until the entity graph is populated and nothing populates it by default. Also documents the two traps that cost real time: maintain's dry_run defaults to true and stores nothing, and MCP_MAINTAIN_SCAN_LIMIT defaults to 2000 taking the first N in storage order, so repeated runs never reach the tail of a larger store. Home had drifted badly: it advertised v10.65.1 and ~1,828 tests, claimed MIT when the project is Apache-2.0, said 12 MCP tools where the registry now has 28, and every repository link pointed at github.com — which sends readers to the suspended mirror rather than Codeberg. Codeberg has no Discussions feature, so the "Question?" link now points at issues instead of a page that does not exist. The What's New section still stops at v10.65.1 and is left for the release workflow to bring forward.

    Henry Krupp committed Aug 8, 2026