Skip to content

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

Rust

Merge pull request #451 from akitaonrails/merge-449

Fabio Akita9cd923b6602b
diff --cc CHANGELOG.md
index e8bc5eaa,34f915d0..62a31059
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -7,23 -7,15 +7,31 @@@ and this project adheres to [Semantic V
## [Unreleased]
+ ### Fixed
+ - The Windows packaging test for the PowerShell wrapper now runs it with
+ `-ExecutionPolicy Bypass`. `-File` loads a script from disk and execution
+ policy governs script files, so on a machine at the Windows client default
+ of `Restricted` the unsigned wrapper was refused and the test failed for a
+ reason unrelated to what it asserts. Test-only; no shipped behaviour
+ changes. (#449)
+
### Added
+- New `gemini_safe_schemas` config flag (env `AI_MEMORY_GEMINI_SAFE_SCHEMAS`, or
+ `gemini_safe_schemas = true` in config.toml) and a matching `?flavor=gemini`
+ MCP URL marker (alias `?flavor=vertex`) serve tool input schemas in the subset
+ Google's `Schema` accepts. `schemars` renders every optional tool argument as a
+ nullable union (`"type": ["integer", "null"]`), but Vertex/Gemini
+ `functionDeclaration.parameters` takes a single `type` and treats `any_of` as
+ exclusive with every sibling key — so a client that forwards our schema
+ verbatim produced `any_of` with `description` beside it and Vertex failed the
+ whole session at `tools/list` with "specified other fields alongside any_of".
+ The dialect collapses those unions to a single `type` plus `nullable: true`,
+ the same normalization Gemini CLI performs client-side, which is why Gemini CLI
+ and Antigravity CLI never hit this and need no marker; pass-through clients such
+ as OpenCode on a Vertex model did. It implies `strip_root_combinators`, and
+ runtime argument validation is unchanged in every dialect. The key is
+ documented in the generated `config.default.toml`, and `docs/mcp-install.md`
+ now collects all three schema dialects in one table. (#450)
- Windows tests moved to their own workflow
(`.github/workflows/windows.yml`), running on every push to `main`,
nightly, on demand, and on any PR labelled `windows`. They were the