Skip to content

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

Rust

Merge branch 'docs/1140-explicit-consolidation-routing' (closes #1140)

AkitaOnRailsc8e577968ddb
diff --cc CHANGELOG.md
index 96169696,887fddc9..0c26f54d
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -95,50 -91,6 +95,57 @@@ and this project adheres to [Semantic V
`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)
## [2.6.0] - 2026-10-07