Skip to content

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

Rust

Merge branch 'land/main-1316' into batch/3.0.3-fixes

AkitaOnRailsf3637bc41555
diff --cc CHANGELOG.md
index 2e4ae1cc,5ad3bd0f..02718a79
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -25,25 -31,19 +31,33 @@@ version in [`docs/changelog/`](docs/cha
user turn: `invocationNum` restarts at 0 each turn, so only the first turn of
a conversation (keyed by `conversationId`) now maps to SessionStart, in the
native, shell and PowerShell hooks. Payloads without a `conversationId` keep
- the previous per-turn behavior.
+ the previous per-turn behavior. A conversation resumed in a new process does
+ not start a new session, so a handoff left meanwhile is read with
+ `memory_handoff_list` rather than injected. (#1306)
- Fixed `llm-test --provider anthropic-oauth` reporting Anthropic's refusal of a
`claude setup-token` token as a plain rate limit: that 429 now carries a hint
- that it is not a real rate limit and names the alternatives, and
- `docs/llm-providers.md` documents the behavior. (#1170)
+ that it is not a real rate limit and names the alternatives, which
+ `docs/llm-providers.md` already describes. (#1170)
+- Fixed the curator report treating a per-user focus slot
+ (`_slots/<operator>/current-focus.md`) as an ordinary slot. It only
+ recognised the shared `_slots/current-focus.md`, so with per-user slots the
+ focus slot got the 30-day stale threshold instead of the 7-day one and was
+ reported three weeks late. (#1314)
+- Fixed multi-page consolidation losing every page of a batch when the
+ model gave one page a path that cannot be repaired: a leading slash, a
+ `..` or `.` segment, or an empty segment. Path validation failed the whole
+ session's consolidation, so the valid pages in the same answer were never
+ written. That page is now skipped with a warning and the others are
+ written, as already happened for paths that fail the portability check.
+ (#1315)
+ - Fixed auto-improve patches losing track of a page's sections after a code
+ block that contains a different fence. A line of three backticks inside a
+ `~~~` block (or a shorter run inside a longer fence) ended the block early,
+ so the headings after it were missed, and a `replace_section` on the
+ section before them replaced those sections too. Profile harvesting had the
+ same flaw: the code after such a line was read as prose and could be
+ harvested as a preference. A fence now closes only on a run of the same
+ character that is at least as long. (#1316)
- Fixed the thin-client commands ignoring a custom `bind`, which could write
into the wrong store. `server_url` defaulted to `http://127.0.0.1:49374`
and was never derived from `bind`, so `ai-memory --data-dir X status` (and