MentisDB Blog

Durable memory for AI agents

MentisDB 0.10.5.50 — Search Invalidation, Bearer Write Fix, Token Delete

July 13, 2026

This release makes large memory chains feel more current: default search hides thoughts that later memory superseded, corrected, or invalidated. It also fixes chain-scoped bearer tokens so they can write (not just read), and lets operators permanently delete revoked tokens from the dashboard and CLI.

Upgrade: cargo install mentisdb --locked --force (or let the daemon self-updater install the tag). Restart the daemon after install. Recommended for long-lived multi-agent chains: MENTISDB_DEDUP_THRESHOLD=0.85.

Search: default invalidation filtering

MentisDB already maintained an invalidated_thought_ids set for thoughts targeted by later Supersedes, Corrects, or Invalidates relations — but that set was only applied when as_of point-in-time queries ran. Normal ranked search kept returning stale duplicates next to their replacements.

As of 0.10.5.50, default retrieval excludes those IDs across query, ranked search, context bundles, recent context, and related REST/MCP surfaces. Pass include_invalidated=true for audit archaeology. Point-in-time as_of still returns thoughts that were valid at that timestamp.

The set only fills when edges exist: agent-written relations (search-first skill) and/or auto-dedup via MENTISDB_DEDUP_THRESHOLD (still off when unset; recommended production value 0.85).

Auth: chain-scoped bearer tokens write correctly

Single-chain bearer tokens could read when clients passed chain_key, but writes that omitted chain_key were authorized against the server default chain and failed with a generic “Bearer token required” message. MentisDB now binds single-chain tokens to their only chain for both authorization and execution. Tokens remain full read+write within scope; there is no separate read-only mode.

Bearer token delete

Revoke still keeps an audit row. Operators can now permanently remove tokens:

Also in this cycle

Verification

Links