Skip to content

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

Rust

Merge branch 'fix/1062-batch-sessionless-drop'

AkitaOnRails084dd339ca56
diff --cc CHANGELOG.md
index c616f56d,789dcefb..12afef47
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -81,32 -79,6 +81,38 @@@ and this project adheres to [Semantic V
ai-jail's own dry-run preflight, so a backend that exists but fails ai-jail's
trust checks is treated as unavailable instead of producing a broken offer.
(#1024)
+- Fixed `continue`, `resume` and bare `ai-memory run` losing sessions launched
+ under a custom native store, such as a second Claude Code config home set
+ with `CLAUDE_CONFIG_DIR`. Automatic harness selection now scans the store the
+ launch resolves (`--env`, then the process environment) instead of always the
+ default one. The client records the store of every session it links, at
+ launch or when the run finishes, in `client-projects.json`. A later launch
+ that cannot find that session and resolves a different store now stops with
+ an error naming both stores and keeps the workstream link, where it used to
+ start fresh and repoint the workstream. `--fresh` still starts a new session.
+ (#1047)
+- Fixed Claude Code sessions never seeing the "broaden when the current project
+ comes up empty" and "maintained pages are evidence, not authority" rules,
+ because Claude Code truncates MCP server instructions at 2,048 characters.
+ The instructions now open with a self-contained core under that cap, and a
+ regression test keeps it there. (#1035)
+- Fixed the macOS menu-bar app showing only a red status item when the bundled
+ server cannot start (for example a port already in use, such as OpenCode v2's
+ default `127.0.0.1:49374`). The menu extra now surfaces the server's fatal
+ `stderr.log` line, and `docs/macos.md` documents the port collision and how to
+ move one side. (#1044)
++- Fixed hook-spool drains stalling behind an event that has no session id.
++ `/hook/batch` reported such an event (anything but a session start) as a
++ failed item, so the drain retried it up to its attempt budget while every
++ event queued behind it waited. The server now acknowledges and drops it,
++ counted as `dropped_invalid` in the ingest metrics, and keeps processing the
++ rest of the batch. (#1062)
+
+### Docs
+- Corrected the Codex support matrix to describe managed-run recovery from a
+ stale shared-daemon run id; `--no-daemon` remains an optional diagnostic and
+ isolation switch. (#987)
+
## [2.5.2] - 2026-10-01
### Added