Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge PR #1006: fix(wiki): write the index file on every checkpoint (#983)
AkitaOnRailsdfed757b4ed7
diff --cc CHANGELOG.mdindex 4eb688a0,2851fd2f..93bc977a--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -8,31 -8,14 +8,38 @@@ and this project adheres to [Semantic V## [Unreleased]### Fixed+- Fixed the shell and PowerShell session-start hooks for Claude Code, Codex,+ Cursor, Gemini CLI, OpenCode, Command Code, Devin, and Antigravity CLI not+ sending the marker's `[briefing]` keys (`briefing`, `briefing_budget`) on the+ handoff request, so a repository with `inject_on_session_start = true` got+ the handoff without its compiled brief on script installs (Docker wrapper,+ `setup-agent`). Only the native `ai-memory hook` command and the Kiro CLI and+ Kimi Code scripts sent them; all now match `docs/marker-file.md`. (#998)+ - Fixed a wiki checkpoint leaving `.git/index` behind the commit it made. A+ path-scoped checkpoint wrote the index file only once every 50 commits, so+ between writes `HEAD` and the working tree held the new page while the index+ still named the old blob, and `git status` from outside the server showed+ every checkpointed page as `MM`; a checkpoint with nothing to commit left a+ stale index the same way. The history itself was always correct. Not specific+ to Windows. (#983, #1006)+### Security+- Fixed `memory_read_page` with `include_related` returning pages from+ projects the caller cannot read under per-project authorization, and walking+ through them to reach others: in multi-user mode an authenticated user without+ a grant saw the paths, titles, kinds, and project names of pages in a+ `restricted` project up to three hops away (never their bodies). `page_links`+ and the graph already hid them; the multi-hop related walk now filters every+ hop the same way. Installs without authorization, and root, are unchanged.+ (#999)+- Fixed CLI `ai-memory message send` (`POST /admin/messages/send`) bypassing+ `message_send` admission: it inserted the message without consulting a+ configured webhook's reject policy or notifying observers, while the MCP+ send path enforced both. It now runs admission at the recipient scope before+ the insert — a rejection returns 403 and stores nothing — and notifies+ observers only after a successful commit, without waiting on nonblocking+ ones. (#756)+## [2.5.1] - 2026-10-01### Fixed