Skip to content

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

Rust

Merge PR #1130: fix(llm): treat truncated and empty structured responses as terminal errors

AkitaOnRails37fcd46e5e0f
diff --cc CHANGELOG.md
index 1f936fa9,15d8a26b..584a4ebe
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -8,30 -8,17 +8,36 @@@ and this project adheres to [Semantic V
## [Unreleased]
### Added
+- Added `ai-memory recover` and a bounded local recovery journal for server
+ outages. Offline managed launches now record only uniquely correlated native
+ session locators; recovery quarantines overlapping spool entries before exact
+ `/hook/batch` transcript replay, journals harnesses without transcript export
+ as spool-only without calling their exporter, retains bounded recovery dedup
+ keys with their sessions,
+ fails closed on terminal drops, and lets only the original owner finish an
+ expired unsuperseded managed run through exact idempotent replay. Backfill
+ and recovery replay now use reserved `recovery_*` idempotency keys, so
+ re-running `backfill --force` over sessions imported by ai-memory ≤2.6.0 (or
+ plain-backfilling a recovery-replayed session) can duplicate those older
+ observations. (#1125)
+ - Added `AI_MEMORY_LLM_COMPAT_DISABLE_THINKING` for the `openai-compat`
+ provider (opt-in, off by default, ignored by every other provider): when
+ set, every chat request carries
+ `chat_template_kwargs: {"enable_thinking": false}`, so thinking-capable
+ local engines (vLLM / SGLang serving Qwen3-class models) spend the output
+ budget on the structured payload instead of a reasoning pass. (#1130)
### Fixed
-- Fixed structured LLM responses stopped at the output budget
- (`finish_reason = "length"`) or returned without usable content: they now
- fail with redacted terminal errors, without copying the response. (#1130)
+- Fixed the cross-project profile rewriting a settled entry whenever new
+ evidence merely agreed with it: a statement now changes only when the ruling
+ or its scope does (the LLM merge reports `changed`), so the line every project
+ receives stays put. The profile digest also moved to the front of the
+ session-start payload, ahead of the handoff and brief that change every
+ session, so it stays in the harness's cacheable prompt prefix; its footer now
+ asks the agent to open an entry before relying on its one-line summary; and
+ topic grouping no longer compares every candidate with every other, which
+ grew quadratically on long-lived installs. See
+ `docs/design-cross-project-profile.md` §11. (#1000)
- Fixed the scheduled auto-improve tests' intermittent empty log captures
(the same latent flaw #1116 fixed for the hooks checkpoint test): a shared
`warn!` callsite's first-in-process execution on a bare thread caches
@@@ -119,57 -102,6 +125,60 @@@
`class=provider status=400`) instead of the error's `Display`, which for a
provider failure includes the upstream response body. The default path
(no `answer`) is unchanged. (#1132)
+- Hermes `post_tool_call` payloads now capture the tool result and a proven
+ outcome. Hermes nests the tool result at `extra.result` and mirrors the
+ call status at `extra.status`; the extractor previously read only
+ top-level `tool_output`/`tool_response`/`result`, so every Hermes
+ observation body read `(no output captured)` and the outcome stayed
+ `unknown` forever. Output now comes from `extra.result` (falling back to
+ `extra.error_message`), and `extra.status` of `ok`/`error` maps to
+ `success`/`error`. Recognized Hermes tool names that execute code or
+ reach the web (`execute_code`, `browser_exec`, `browser_navigate`,
+ `web_extract`, `web_fetch`, `delegate_task`) classify as `non-file`
+ instead of `unknown`, so their output is no longer dropped by the
+ unknown-family body shortcut. Payload shape verified against Hermes
+ `agent/shell_hooks.py` on 2026-10-07. (#1123)
+- Fixed the Pi extension sending `notifications/initialized` as a JSON-RPC
+ request with an id: JSON-RPC 2.0 and MCP notifications do not carry an id and
+ expect no response body, which caused the server to emit `-32601`
+ method-not-found warnings on every Pi launch. The generated extension now
+ uses `mcpNotify` to send notifications without an id and accept empty
+ successful HTTP responses without failing JSON parsing. (#1136)
+- Fixed the shell (`hooks/_lib.sh`) and PowerShell (`hooks/lib/ai-memory-hook.ps1`)
+ hooks dropping live events and deleting spooled entries on a `408`, `425` or
+ `429` response, which they treated as a permanent rejection. They now keep
+ those events queued like other transient failures, matching the native
+ spool (`429` retries for free; `408`/`425` retry under its attempt budget
+ since #1092), and a drain pass stops without deleting queued entries. (#1146)
+- Fixed expired pages still showing in `page_links`, `related_walk` and
+ `cross_project_edges`: the web link panel, `memory_read_page
+ include_related`, and the web / `/api/v1` graph view now hide a page (and
+ any edge touching it) once its TTL has passed. Search, recent, briefing, and
+ `graph_neighbors_for_project` already applied the retrieval TTL
+ (`expires_at` is null or still in the future); these three queries only
+ filtered `is_latest`. An expired neighbour is neither returned nor
+ walked through. Exact-path reads of an expired page are unchanged. (#1141)
+- Fixed the session-aware MCP bridge failing on Docker-wrapper installs: the
+ wrapper sent `mcp-bridge` to the helper container, where the registered
+ `127.0.0.1` server URL is unreachable, so every session started without
+ ai-memory's MCP tools. The wrapper now runs `mcp-bridge` through its
+ checksum-verified native host client, which also repairs existing entries.
+ (#1147)
+- Fixed the cross-project profile promoting a single project's "always" /
+ "never" / "by default" sentences as general preferences: only an explicit
+ cross-project scope ("in all my projects", "every project", "everywhere",
+ and the Portuguese equivalents) now waives the `min_projects` threshold,
+ in both the zero-LLM detector and the LLM classifier prompt. (#1148)
+- Fixed explicit in-session "consolidate this session" requests reaching the
+ server's model: the routing instructions and the managed learning and
+ durable-pages skills now send them to the agent route (`memory_read_session_observations`, then
+ `memory_write_page` with `session_id`) and give the agent the server's
+ multi-page layout (session, concept, decision, gotcha and rule pages, at
+ most five). `memory_consolidate` stays for other sessions and headless
+ runs. (#1140)
++- Fixed structured LLM responses stopped at the output budget
++ (`finish_reason = "length"`) or returned without usable content: they now
++ fail with redacted terminal errors, without copying the response. (#1130)
## [2.6.0] - 2026-10-07