Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs(changelog): record the memory_read_page not-found error class

Rudy Mizrahi Celekli75453f99fdfa
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 9839b544..c1b58b7f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -223,6 +223,16 @@ version in [`docs/changelog/`](docs/changelog/):
relay and wiki sync companions take the same `rustls-webpki` bump.
### Fixed
+
+- `memory_read_page` now answers a missing read target with `invalid params`
+ (-32602) instead of an internal error (-32603). A page absent under the
+ resolved scope, and a query that matched nothing, are caller-fixable: the
+ store answered, there is simply nothing there, and a client reads -32603 as
+ "retry". `memory_status` and `memory_read_session_observations` already
+ answer -32602 for an unknown project or session. The messages and the
+ auto-resolved-scope hint are unchanged, and a genuine disk or store failure
+ on the same path still answers -32603.
+ ([#1544](https://github.com/akitaonrails/ai-memory/pull/1544))
- Memory health no longer counts a link from a superseded or TTL-expired page
version as a reference. A page whose only inbound link was removed by a later
edit was reported as linked, because the old version's `links` row survives