Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge PR #887 into main
AkitaOnRails1c9bc40fcb4b
diff --cc CHANGELOG.mdindex 8c194578,32f42a02..39186f2d--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -20,29 -20,14 +20,37 @@@ and this project adheres to [Semantic Vquery before falling back. (#873)### Fixed+- `ai-memory run`'s auto-wire no longer overwrites an installed session-aware+ Claude Code MCP bridge with the static HTTP registration. The auto-wire+ sentinel is keyed by client version, so the MCP step re-ran on every upgrade+ and replaced the `ai-memory` entry wholesale; a user who had run `install-mcp+ --client claude-code --session-aware` lost the bridge on the next `ai-memory+ run` after an upgrade, silently disabling `[auto_scope] per_session` for their+ MCP calls. Auto-wire now detects an existing session-aware bridge and keeps+ it. (#888)+- After a managed launch, `ai-memory run` imported the newest native session+ in the checkout even when a hook in the launched harness had linked the+ run's own session, so a concurrent launch in the same checkout could hand it+ another transcript. The server now records when a session is linked during+ a run (schema migration V67, adding `managed_runs.native_session_linked_at`)+ and reports it in the run status, and the launcher imports that session+ when this checkout's store holds it (a process the child starts inherits+ the run id; OpenCode is checked by the session's recorded directory). An+ older server reports no link and keeps the previous behavior. (#820)+- On Windows, OpenCode 1 and 2 sessions are found again from their checkout:+ OpenCode records a session's directory with forward slashes+ (`C:/Users/me/repo`), so matching only the backslash checkout path found+ none. `ai-memory doctor` reported `0 local` for OpenCode while it captured+ sessions there, and `ai-memory run` / `show` could neither discover nor list+ a native OpenCode session to resume. (#882)+ - Grok Build CLI hooks capture on Windows again. Grok evaluates+ `~/.grok/hooks/*.json` commands with PowerShell, as Codex does (#515), so+ the double-quoted executable path in command position parsed as a string+ expression and every hook exited 1 with a ParserError: sessions ran with+ the hook installed and nothing was captured. The Windows command now+ carries PowerShell's `&` call operator for Grok too; re-run+ `ai-memory install-hooks --agent grok --apply` to rewrite an existing+ install. (#887)- The Linux/macOS Docker wrapper now keeps its native host client in`${XDG_DATA_HOME:-~/.local/share}/ai-memory/native-runner` instead of`~/.cache/ai-memory/native-runner`. `ai-memory run` auto-wires hooks whose