Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge PR #867 into release/2.5
AkitaOnRailsd897d2d7f683
diff --cc CHANGELOG.mdindex 583d363e,a3b4e28b..dad03bb4--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -80,16 -80,12 +80,22 @@@ and this project adheres to [Semantic V(not bare JSON 401), forms call existing `POST /auth/login` /`/auth/password` / `/auth/logout`, and `--web-ui-dir` custom SPAs stayunchanged. (#811)+- `docs/jev-reranker-adapter.md` documents a stdlib-only adapter+ (`docs/examples/jev-reranker-adapter/jev_rerank_shim.py`) that serves the+ `AI_MEMORY_RERANKER=llm` request leg from a Jev `/v1/systemone` judge+ endpoint while reverse-proxying consolidation/lint/bootstrap traffic to+ the configured provider unchanged. In the contributor's own 102-query+ golden-set benchmark the judge matched the hosted reranker's+ hit@1/MRR/NDCG@10 (0.778/0.838/0.873 vs 0.778/0.840/0.875) at 0.205 s+ mean latency instead of 20.2 s — in that run the hosted mean sat on the+ server's 20 s completion timeout, which made the reranker stall every+ query before falling back. (#873)+ - MCP tool calls from OpenCode 2 (2.0.4+) are routed by the native session id+ the client sends in `params._meta["ai.opencode/sessionID"]`, ahead of the+ `Mcp-Session-Id` transport header, which OpenCode shares across every+ session in a directory. Concurrent OpenCode sessions in different projects+ no longer read each other's active project; explicit `workspace`/`project`+ arguments still win and `X-Memory-Actor-Session-Id` keeps precedence. (#864)### Changed- Grok Build CLI shows a pending handoff, and an opted-in `[briefing]`, as