Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge pull request #804 from kevin9327: fix(config): use USERPROFILE as home when HOME is unset
AkitaOnRailse3ea5f0c0f3d
diff --cc CHANGELOG.mdindex 8ca67696,23bc6425..7588ed82--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -7,33 -7,13 +7,39 @@@ and this project adheres to [Semantic V## [Unreleased]+### Security+- Bumped `rmcp` to 2.x (2.2.0), resolving three MCP transport advisories:+ GHSA-9pj6-vhgr-3mwh (unauthenticated Streamable-HTTP session-table leak /+ DoS), GHSA-33f5-2c5q-wgwj (missing OAuth resource-field validation), and+ GHSA-9g45-5xwm-f3wc (custom headers leaking to cross-origin redirect+ targets). Behavior-preserving: the only source change is the+ `rmcp::model::Content` → `ContentBlock` rename (imported under the prior+ name), the feature set is unchanged, and the 23-tool MCP surface is+ unaffected. (#794)++### Docs+- `docs/llm-providers.md` now covers the `opencode` LLM provider, which has+ shipped since 1.x but was missing from the recommended-defaults table:+ `OPENCODE_API_KEY` as the only credential, Go as the default endpoint, Zen+ via `AI_MEMORY_LLM_BASE_URL`, the built-in default model, per-catalogue+ model ids, and which model goes through the Responses endpoint (#763).+### Fixed+- The Windows Docker wrapper (`bin/ai-memory.ps1`) now forwards the same+ provider credentials and host-config env vars as the POSIX wrapper into the+ helper container. A host-exported `GEMINI_API_KEY` / `GOOGLE_API_KEY`,+ Copilot token, `OPENCODE_API_KEY`, `CLAUDE_CONFIG_DIR`, or+ `AI_MEMORY_WORKSTREAM_ID` previously never reached `Config::load`, so+ `llm-test`, Copilot auth, OpenCode, and a relocated Claude config all+ reported "not configured" on native Windows Docker Desktop even though the+ same export worked through `bin/ai-memory`. The POSIX wrapper also now+ forwards `OPENCODE_API_KEY`. (#803)+ - `Config::load` now treats Windows `%USERPROFILE%` (then `dirs::home_dir`) as+ the operator home when `AI_MEMORY_HOME` and `$HOME` are unset. Native+ Windows often has no `HOME`, so the #103 catch-all guard — skip a stored+ `repo_path` equal to the user profile so it cannot prefix-match every+ project beneath it — was inert there and a home-directory project could+ swallow unrelated cwds. (#804)## [2.3.2] - 2026-09-20