Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

Merge audited PR #1510

AkitaOnRailsf5a6f4d51ec6
diff --cc CHANGELOG.md
index cc963dfa,b25da155..b73e276d
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -98,18 -93,17 +98,29 @@@ version in [`docs/changelog/`](docs/cha
as its JSON entry.
([#1490](https://github.com/akitaonrails/ai-memory/issues/1490))
+- Moved the commented `[run.profiles.work.env]` and `[ingest]` examples in the
+ default config, the `config.toml` that `ai-memory init` writes and the
+ native packages install, below its top-level keys. A TOML table header owns
+ every key after it, so uncommenting one of those tables and a top-level
+ example below it, such as `reranker`, `capture_assistant` or
+ `gemini_safe_schemas`, put that key inside the table: `[ingest]` ignored it
+ without a warning, and the run profile's env map either failed the config
+ load or exported the key to the harness. A config written by an earlier
+ release keeps its layout; move an uncommented table there below the last
+ top-level key.
+ ([#1506](https://github.com/akitaonrails/ai-memory/issues/1506))
+
+ - Kept the user PATH's `%VAR%` entries and its `REG_EXPAND_SZ` type when
+ `install.ps1` and the desktop installer add their directory to it, and in
+ the manual PATH steps in `docs/windows.md`. They read the value with
+ `[Environment]::GetEnvironmentVariable`, which expands every variable, and
+ wrote it back with `SetEnvironmentVariable`, which stores it as `REG_SZ`.
+ An entry such as `%JAVA_HOME%\bin` stopped following its variable, and one
+ whose variable the installer did not have stayed as literal text that
+ Windows never expands. A PATH an earlier install already rewrote keeps its
+ expanded entries.
+ ([#1509](https://github.com/akitaonrails/ai-memory/issues/1509))
+
## [3.1.2] - 2026-10-20
### Fixed