Skip to content

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

Rust

Merge main into fix/workstream-search-evidence-label

AkitaOnRails7bd193d1d609
diff --cc CHANGELOG.md
index ed8b6d2f,84fc7350..6fb3ebbc
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -13,11 -13,84 +13,89 @@@ version in [`docs/changelog/`](docs/cha
### Fixed
+- `ai-memory workstream-search` now labels a historical tool call or tool
+ result as completed evidence, as the managed-workstream docs describe. Its
+ text output used the event's role, which every transcript adapter sets to
+ `assistant` on a tool call, so a past command read like an assistant action
+ still to run (#1629).
+ - `install-hooks --agent grok` run from the home directory no longer stops
+ with "Grok project configuration ~/.grok/config.toml may override
+ GROK_HOME". With the default `GROK_HOME` that file is Grok's own user
+ config, which Grok reads only as the user layer (`grok inspect` reports no
+ project layer there), so it is no longer mistaken for a project overlay. A
+ real overlay is still refused, including `~/.grok/config.toml` when
+ `GROK_HOME` points elsewhere (#1636).
+ - The OpenCode, OpenCode 2, OpenClaw, Pi and OMP integrations installed with
+ `--capture-mode allowlist` no longer send the handoff (or OpenCode's recap)
+ request from a repository without a `.ai-memory.toml` marker. They already
+ dropped its capture, but the server answers that request by resolving the
+ directory into a project, so opening one of these agents in an unmarked
+ directory left an empty project named after it. The native hook already
+ returned before the request; these integrations call the server directly
+ (#1641).
+ - An auto-improve full-page proposal is now rejected when its body has two
+ identical headings or more than one H1, the two checks the patch path
+ already applies to every body it materializes. A full-page proposal is
+ auto-approved whenever approval is not required, and the page it wrote was
+ then permanently un-patchable: the patch path refuses on the target's own
+ duplicate headings before it materializes any edit, so no later proposal
+ could repair it (#1635).
+ - `memory_feedback` now answers a path with no current page in the resolved
+ project with `invalid_params` (-32602) rather than `internal_error`
+ (-32603). An absent caller-supplied target is the request being wrong, not
+ the server failing, and -32603 tells a client to retry a path that can
+ never succeed. This was the last tool reporting an absent target as a
+ server fault; genuine store failures are still `internal_error`, and the
+ message is unchanged (#1634).
+ - A Qwen Code `UserPromptSubmit` body is now capped and scrubbed before the
+ native hook spools it. The per-event cap covered `prompt`, `message` and
+ `text`, but Qwen's prompt arrives in `submitted_prompt` — the field the
+ harness-specific extraction reads — so a Qwen prompt reached the local spool
+ and the server at full length with no client-side redaction pass. The field
+ is now capped alongside its siblings; nothing falls back to the generic
+ `prompt`, so submission provenance is unchanged (#1633).
+ - The forget sweep now keeps an already-compacted page terminal when
+ `compact_cold_episodic` is off — the default everywhere. The guard that made
+ a page carrying the V65 `compacted_at` marker "neither re-compacted nor
+ evicted" sat inside the compaction arm only, so with compaction off such a
+ page was tombstoned and then hard-deleted. The marker is not A2's alone: the
+ A3 cold-cluster dedup merge-note stub and the B2 dream pass both stamp
+ `compacted: true` under their own flags, so the durable residue a merge chose
+ to keep could be destroyed without anyone enabling compaction. A
+ non-compacted cold page is still evicted exactly as before (#1632).
+ - A project whose every page has passed its TTL is read as new again when
+ the profile digest sizes itself. The newness probe was the one `pages` read
+ in the profile module without the expiry guard its three siblings apply, so
+ such a project still counted as having memory: it got the smaller
+ established-project digest and lost the note offering
+ `ai-memory profile apply`, with no live page left to show for it (#1631).
+ - The first start after the 3.2.0 upgrade no longer slows down as the
+ one-time CJK index backfill (V87) progresses. Each batch filtered the source
+ table from its first row again, so the pass probed every row it had already
+ indexed once more per batch: quadratic in the row count, and hours of
+ startup on a store with 1.6 million observations while `serve` answered
+ nothing. Each batch now resumes after the last rowid it indexed, so every
+ row is examined once (#1652).
+ - Restoring a page from a checkpoint (`/admin/restore-page`) no longer
+ rewrites the restored file's `generated.at` to the current time when the
+ checkpoint is already OKF-conformant. The restore now keeps the
+ checkpoint's own timestamp when conformance leaves the rest of its
+ frontmatter unchanged and the file on disk holds other content, so a
+ checkpoint emitted by ai-memory restores byte for byte whatever the clock.
+ When the file on disk already holds the same content, its timestamp is kept
+ so file and row stay aligned; checkpoints that need conformance still go
+ through the existing inheritance and stamping rules (#1671).
+ - The native Windows Docker wrapper now recognizes `upgrade` after valid
+ `--config` or `--data-dir` global options and pulls the image instead of
+ forwarding `upgrade` into the helper container. Unknown and malformed
+ options still reach the CLI parser (#1667).
+ - `ai-memory run codex` no longer starts a new session when Codex has
+ compressed the linked rollout. Codex keeps a rollout it has not written for
+ a week as `rollout-*.jsonl.zst`, which the launcher did not recognize, so it
+ reported the session as missing and repointed the workstream to a fresh one.
+ The compressed copy is now read for the resume, the pre-launch baseline and
+ the transcript import, and the plain file wins when both exist. `backfill`
+ and the session listings see compressed Codex sessions too (#1653).
- Updated tokio to 1.54.1 in the server, relay, importer and wikisync
lockfiles. 1.52.3 and the 1.53.x releases before 1.53.3 fall inside
RUSTSEC-2026-0386, an unsound advisory for `AsyncFd` constructors that