Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge remote-tracking branch 'origin/main' into merge-435
AkitaOnRails1e058a1402ac
diff --cc CHANGELOG.mdindex 4edb8975,75456dc8..db7b5845--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -8,15 -8,18 +8,27 @@@ and this project adheres to [Semantic V## [Unreleased]### Added+- New `llm_timeout_secs` config key (env `AI_MEMORY_LLM_TIMEOUT_SECS`, or+ `llm_timeout_secs = 900` in config.toml) overrides the per-request timeout+ every chat provider applies to its HTTP calls — previously hardcoded at+ 300s per provider. Slow hosted gateways (observed with free aggregator+ tiers whose long completions exceed five minutes) failed every request with+ `http: error sending request` once generation crossed the ceiling, so LLM+ consolidation exhausted its retries and left heuristic pages behind; now+ operators raise the bound at startup instead. The Copilot token exchange+ is bounded by the same value, and the 300s default is unchanged ([#435]).+ - Added a `flake.nix` so NixOS and Nix users can build and run ai-memory+ without the Rust toolchain or Docker: `nix build`, `nix run . --+ --version`, or `nix develop` for a dev shell. The build is self-contained+ (SQLite bundled, libgit2 vendored, rustls with webpki-roots — no OpenSSL,+ no system-library hunting). The flake skips the packaging test suite+ because those tests exercise the Docker-wrapper shell script and need+ `docker`/`podman` on PATH; the rest of the workspace tests can be run via+ `nix develop -c cargo test --workspace`. Flake inputs are pinned to+ explicit revisions rather than floating branches, so the build is+ reproducible, and a `nix` CI job builds the flake and runs the resulting+ binary whenever a Nix build input changes plus weekly, so the packaging+ cannot rot unnoticed. ([#405])- New `strip_root_combinators` config flag (env `AI_MEMORY_STRIP_ROOT_COMBINATORS`,or `strip_root_combinators = true` in config.toml) strips root-level`anyOf`/`oneOf`/`allOf` from MCP tool input schemas on every `tools/list`.