Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge remote-tracking branch 'origin/pr/1485'
AkitaOnRails4b6034f44383
diff --cc CHANGELOG.mdindex c426082e,b823ec7f..3f2ed1e9--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -234,15 -218,11 +234,20 @@@ version in [`docs/changelog/`](docs/cha`as_of` that is not an ISO-8601 instant, instead of misreporting them asinternal server errors.([#1468](https://github.com/akitaonrails/ai-memory/issues/1468))+- Built the web UI's templates without askama's `config` feature, which only+ reads an `askama.toml` that ai-memory does not have. The unmaintained+ `basic-toml` (RUSTSEC-2026-0374) is no longer a dependency, and templates+ render as before. ([#1482](https://github.com/akitaonrails/ai-memory/issues/1482))+- Copied the release into place in `install.ps1` instead of moving it, so an+ antivirus scan that still holds the just-verified `ai-memory.exe` no longer+ stops a Windows install with "the process cannot access the file because it+ is being used by another process".+ ([#1480](https://github.com/akitaonrails/ai-memory/issues/1480))+ - Invoked Gemini CLI's native Windows lifecycle commands with PowerShell's+ call operator. Gemini CLI 0.23.0 and later run hook commands through+ PowerShell, where the quoted `ai-memory.exe` path failed to parse, so every+ hook exited with an error and the session captured nothing.+ ([#1484](https://github.com/akitaonrails/ai-memory/issues/1484))## [3.1.1] - 2026-10-17