Skip to content

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

Rust

Merge PR #1083: fix(mcp): enforce per-user slot namespaces in memory_delete_page

AkitaOnRails6859556fbd2e
diff --cc CHANGELOG.md
index 2d1810f8,133150ce..ae54d020
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -178,20 -178,6 +178,26 @@@ and this project adheres to [Semantic V
Documented the observed attach-hook behavior, early-exit import boundary and
fallback validation limits.
(#1052)
+- Fixed the provider-health wrapper dropping the caller's operation id: its
+ `complete_with_operation_id` and `complete_structured_raw_with_operation_id`
+ fell to the trait defaults, so every retry of one logical operation got a
+ fresh id and, for OpenCode, a new session header on every call. The wrapper
+ now forwards both. (#1085)
+- `backfill` works with a non-root key on a multi-user server. Its emptiness
+ check used the root-only `/admin/sessions/by-agent` route, so every
+ developer's own key got 403; on a 403 it now asks the grant-checked
+ `GET /api/v1/workspaces/{ws}/projects/{p}/sessions` instead. (#1086)
+- The sanitizer now redacts `*_KEY_ID`, `*_PASSPHRASE`, `*_SIGNING_KEY`,
+ `*_PEPPER` and `*_SALT` assignments (e.g. an S3 `…_ACCESS_KEY_ID`, an auth
+ token pepper) and dotless base64 JSON tokens such as Cloudflare tunnel
+ tokens (`eyJ…`, 40+ characters); SHAs, UUIDs and short `eyJ` fragments are
+ left alone. (#1084)
++- Fixed `memory_delete_page` bypassing per-user slot namespace routing and
++ access checks when `[slots] per_user` is active. Non-admin callers deleting a
++ generic slot path (`_slots/current-focus.md`) are now redirected to their
++ personal slot namespace instead of removing the shared project-wide slot, and
++ deleting directly inside another operator's slot namespace is rejected with an
++ invalid request error. (#1083)
### Security
- Fixed GHSA-7qj3-7wqw-m5w6: in multi-user mode a database user without a