Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge PR #1137: fix(hooks): send Pi initialized notification without request id
AkitaOnRails402ce6229041
diff --cc CHANGELOG.mdindex 33553cab,0f50e0cc..5b154dbc--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -95,19 -97,6 +95,25 @@@ and this project adheres to [Semantic V`class=provider status=400`) instead of the error's `Display`, which for aprovider 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)## [2.6.0] - 2026-10-07