Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge remote-tracking branch 'refs/remotes/audit-open/1565'
AkitaOnRails35bbcfce49ba
diff --cc CHANGELOG.mdindex 81660392,0cc6bd92..38e00892--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -11,72 -11,32 +11,98 @@@ version in [`docs/changelog/`](docs/cha## [Unreleased]+## [3.2.1] - 2026-10-22++### Fixed++- The `user grants` and `project grants` tables no longer misalign on a+ workspace, project or user name outside ASCII. Column widths were measured+ in bytes while the formatter pads in characters, so a row such as+ `default/café` was padded one column too far and its `USERNAME` and+ `LEVEL` cells sat right of every other row's.+ ([#1564](https://github.com/akitaonrails/ai-memory/pull/1564))+- Fixed a 3.2.0 regression that serialized local document embedding and+ dropped the vector stream from queries that raced a document embed: the+ local embedder's capacity was hardcoded to two slots (one document, one+ query), and a query finding both busy degraded instantly to lexical+ search. The scheduler is now sized from the CPU (half the available+ parallelism, clamped to between 2 and 6 slots, documents capped at+ capacity minus one so a slot stays query-reserved), and a query waits up+ to 250 ms for a slot before degrading. On the affected LongMemEval-S+ question set this restores query latency (p50/p95 66/87 ms vs 3.2.0's+ 118/295) and ingest throughput; the reported hit@5 delta (0.947 → 0.938)+ traces to rank-boundary questions that flip between identical runs, not+ a deterministic ranking change (#1580).++- Fixed `ai-memory run` (and `show`, `continue`, `resume`, `workstreams`,+ `rename-workstream`) failing on Windows Docker installs with "managed+ claude executable `claude` was not found in the host PATH": the PowerShell+ wrapper sent every subcommand into the Linux helper container, which has no+ host CLIs. It now intercepts the same six commands `bin/ai-memory` does and+ runs them through the native Windows client, resolved from+ `AI_MEMORY_NATIVE_BIN` or the documented+ `%LOCALAPPDATA%\Programs\ai-memory` install location, inheriting+ `AI_MEMORY_SERVER_URL` (an explicit value wins) and exiting with the+ child's code. A missing client fails with the documented installer command+ instead of entering the container; the POSIX wrapper's Git Bash refusal+ points at the same installer; and the missing-harness error's Docker+ advice is now OS-aware: on Windows it names the native-client installer+ rather than `ai-memory upgrade`, which in the `.ps1` wrapper only pulls+ the image. Managed launches keep the hook/MCP wiring rendered through the+ container (the wrapper sets `AI_MEMORY_RUN_AUTOWIRE=false` for the+ intercepted commands unless the operator set it). (#1545)++- Corrected four statements in `SECURITY.md` that no longer matched the+ code, plus two clarifications in the same sections (#1561). The+ `AI_MEMORY_ALLOWED_HOSTS` default is `localhost`, `127.0.0.1`, and `::1`;+ request bodies are capped at 10 MB on `/mcp`, `/hook` and `/workstream/*`,+ 32 MB on `/admin/*`, and 2 MB elsewhere; the auth ladder is anonymous,+ root bearer, proxy-asserted user, and `aim_` database-user tokens (the+ server itself never validates OIDC tokens, and the doc no longer says it+ does); and the "no per-user or per-project ACLs" claim became the current+ truth about per-project access modes and grants, including that+ proxy-asserted identities are not subject to them. The bearer-check note+ now lists the routes that are public by design (`/healthz`, `/auth/login`,+ `/auth/recovery`, `/favicon.ico`, custom `/web` static assets).+- Completed the egress inventory in `DATA_HANDLING.md` and documented the+ default first-start behavior it omitted (#1560). A default install now+ says plainly that the local embedder downloads its three model files+ (~87 MB, sha256-pinned) from `huggingface.co` in the background on first+ start, that nothing stored is sent, and how to avoid it+ (`embedding_provider = "none"` or offline pre-seeding). The export table+ gained the rows it was missing: the `llm_provider` pipeline (including+ the `codex`, `copilot` and `cursor` CLI-backed providers), the `copilot`+ embedding provider, and `[[admission_webhooks]]`, plus notes on+ `ai-memory upgrade`'s GitHub release query, the OAuth/OIDC login flows,+ and remote `server_url` topologies. `docs/airgapped-install.md`'s+ runtime summary was corrected to match.++ ### Security+ - A malformed OAuth entry in `auth.json` no longer prints the stored value in+ its error. When a field held a value of the wrong type, such as a token+ written into `expires` by a hand edit or a provisioning script, the parse+ error quoted the token, and from there it reached terminals, CI logs and+ captured hook output. The error now names the type it found with the value+ replaced by `<redacted>`.+ ([#1565](https://github.com/akitaonrails/ai-memory/pull/1565))++ ### Fixed+ - Every command except `hook` and `mcp-bridge` now warns, naming the variable+ but not its value, when `HTTPS_PROXY`, `HTTP_PROXY` or `ALL_PROXY` (or a+ lower-case spelling) is set to something the HTTP client cannot use: bytes+ that are not UTF-8, such as a Latin-1 password, a URI with an unencoded+ space or non-ASCII character, or an unsupported scheme. The client skips+ such a value and connects directly, so provider and login requests used to+ time out on a network that blocks direct egress, or bypass a required proxy+ where it does not, with nothing pointing at the proxy setting.+ ([#1565](https://github.com/akitaonrails/ai-memory/pull/1565))+ - `init`, `auth` and `auth enable` print paths on Windows without the `\\?\`+ verbatim prefix of the canonical data dir, in their output and their errors,+ as the hook and service commands already did, and so does the+ `ai-memory starting` line every command logs. A path copied from those+ messages now works in `cmd` and in scripts that look for it.+ ([#1565](https://github.com/akitaonrails/ai-memory/pull/1565))+## [3.2.0] - 2026-10-21### Added