Skip to content

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

Rust

Merge PR #990: status discriminant on memory_handoff_accept (fixes #988)

AkitaOnRails7e1793988141
diff --cc CHANGELOG.md
index 7db27c42,4f002734..ed097e94
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -270,9 -260,16 +270,17 @@@
`docs/airgapped-install.md`, and the README docs table. The on-box
`ai-memory backup --to <tarball>` command
(`docs/lifecycle-ops.md#backup`) is unchanged. (#950)
-
+ - `memory_handoff_accept` returns a `status` next to `handoff`: `claimed` when
+ the call took the handoff, `consumed_by_hook` when the calling session's own
+ SessionStart already claimed it (so it is in that session's context), and
+ `none_pending` when nothing is left to claim. A bare `{"handoff": null}` used
+ to cover both of the last two. `consumed_by_hook` needs the session id the
+ hook claimed under, which Claude Code's `install-mcp --session-aware` bridge
+ and OpenCode 2 forward; the answer stays inside the caller's project and
+ handoff ownership, so a forwarded id cannot report another operator's or
+ another session's claim. The `handoff` field is unchanged. (#988, #920)
+
### Changed
- `ai-memory purge-session` without `--confirm` now previews what a confirmed
purge would delete before refusing, the same way `purge-project` does (#945):