Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge commit 'refs/audit/pr-1705'
AkitaOnRailsd3700c832fa2
diff --cc CHANGELOG.mdindex 47265edb,5c784f02..cd9d0e04--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -11,52 -11,23 +11,57 @@@ version in [`docs/changelog/`](docs/cha## [Unreleased]-### Added--- `GET /admin/status` and `ai-memory status --json` now carry a- `consolidation` block: the queue counts plus up to 20 `failed_sessions`- (`session_id`, `attempts`, `failed_at_us`, scrubbed `last_error`), newest- first. A consolidation run that gives up after its retries now has a- machine-readable record with the session ids needed to re-run it, instead of- only a journal line and the `/health` panel's count — which also resets with- the process. The web health panel's own view stays counts-only, and an older- server's status shape is unchanged (#1692).-+ ### Fixed++ - `ai-memory backup` and `ai-memory backup-agents` now carry a size that+ would round to `1024.00` of the current unit into the next one. A backup- of 1 MiB − 5 bytes was printed as `1024.00 KiB` (#1705).++ of 1 MiB - 5 bytes was printed as `1024.00 KiB` (#1705).+++## [3.2.4] - 2026-10-25++### Security++- A restricted project now stays closed when its access-mode or grant query+ fails. The common authorization resolver previously degraded these store+ failures to an open project, so an unrelated authenticated user could gain+ access during a database fault. Unknown projects and forward-unknown access+ modes retain their compatibility behavior, and normal root, creator and+ grant access is unchanged.+- Human-auth endpoints now log unexpected store and task failures server-side+ and return a stable `authentication unavailable` response. Login and+ recovery previously returned raw SQLite or task error text before the caller+ authenticated; password-change conflicts also no longer expose store errors.++### Fixed+- `ai-memory move-session` now refuses explicitly empty scope flags+ (`--from-project`, `--from-workspace`, `--to-workspace`, and `--to`) before+ sending any request. Passing an empty string like `--from-project ""` previously+ bypassed the flag check while falling back to deriving the project from the+ current working directory, which triggered an unintended batch move of all+ sessions from the current repository (#1698).++- `ai-memory delete-page` now refuses explicitly empty scope flags (`--workspace`+ and `--project`) as well as an empty `--path` before sending any request.+ Passing an empty `--project ""` previously bypassed the flag check while falling+ back to deriving the project from the current working directory, which risked+ deleting the page from the local repository (#1700).++- `ai-memory rename-workstream` now refuses explicitly empty scope flags+ (`--workspace` and `--project`) as well as empty workstream names (`--from`+ and `--to`) before inspecting the repository or sending any request.+ Passing an empty `--project ""` previously bypassed the flag check while+ falling back to resolving the project from the current working directory (#1702).++- Fixed `ai-memory setup` treating another service's HTTP 200 response as a+ healthy ai-memory server. Setup now checks the bounded `/healthz` JSON,+ reports an occupied address with port/configuration remedies, and skips+ MCP/admin probes when the health response is unrecognized (#1647).++- Preserved repository edits saved while `ai-memory-wikisync export --apply`+ fetched server pages. Export now rechecks each file before replacing it,+ as two-way sync already did, and refuses a changed file even with `--force`+ without advancing its export state (#986).-- Codex's own memory-writing agent no longer appears as captured sessions.Codex runs a background "memory writing agent" from `$CODEX_HOME/memories`(the default `~/.codex/memories`) to consolidate its memory; the hooks