Skip to content

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

Rust

Merge PR #1295: fix(hooks): keep draining the spool past a refused credential

AkitaOnRailsbe331ac37dda
diff --cc CHANGELOG.md
index c0d49491,e893c255..79c07f4a
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -59,19 -35,13 +59,26 @@@ version in [`docs/changelog/`](docs/cha
embedding backfill ran, which by default is only at the next server
start. These paths now embed each written page the same way
`memory_write_page` does. (#1258)
+- Fixed `ai-memory run` reporting `server unavailable` for a heartbeat the
+ server answered and rejected. A heartbeat is rejected once its managed run
+ stops being active, which on a workstation usually means a later `run`
+ prepared a workstream and expired every active run whose lease had already
+ passed. The launcher printed the outage notice for a failure of any kind and
+ sent the real reason to a `debug` line nobody sees at the default level, so a
+ server that answered `409 managed run lease is not active` in about a
+ millisecond read as an outage. The notice now carries the server's own reason
+ for a rejection, and keeps the outage wording only for a server the launcher
+ could not reach. (#1277)
+- Updated rustls to 0.23.46 for RUSTSEC-2026-0346, -0347, -0348 and -0349,
+ in the server and in the importer, relay and wikisync companions, and the
+ importer's anyhow to 1.0.104 for RUSTSEC-2026-0190. (#1286)
+ - Fixed the hook spool delivering nothing after `ai-memory auth enable`
+ while it still held entries captured before the switch. Those entries
+ carry no credential and sort first, so their batch was refused with `401`
+ and the drain stopped there, never posting the entries behind them that
+ carry the accepted token. A refused credential now only holds back the
+ entries that carry it: they stay queued, the first of them charged once
+ per pass, and the drain carries on with the rest. (#1283)
## [3.0.0] - 2026-10-13