Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge branch 'main' into pr195-fix
AkitaOnRails9fc79bcf9969
diff --cc CHANGELOG.mdindex cac600d3,c1332c61..b1d42639--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -18,28 -18,9 +18,30 @@@ and this project adheres to [Semantic V`.ai-memory.toml` ([#194]). Supported native hooks and generatedOpenCode/OMP/Pi/OpenClaw integrations apply the policy before local spool ornetwork delivery; `ai-memory hook --check-capture` safely reports a bounded- local decision. This changes no MCP tools and needs no database migration.+ local decision. Generated integrations resolve relative file-tool paths from+ the event `cwd`, including nested working directories, rather than from the+ marker directory. This changes no MCP tools and needs no database migration.+- Kimi Code CLI is now a supported MCP + lifecycle-hook integration+ (`--client kimi-code` / `--agent kimi-code`, alias `kimi`). `install-mcp`+ merges an `mcpServers` entry into `~/.kimi-code/mcp.json` with a plain `url`+ (Kimi Code treats `url` with no `transport` field as streamable HTTP) plus+ optional bearer `headers`. `install-hooks` merges `[[hooks]]` entries into+ `~/.kimi-code/config.toml`, preserving the provider/model settings the same+ file holds, and covers 9 events: `SessionStart`, `SessionEnd`,+ `UserPromptSubmit`, `PreToolUse`, `PostToolUse`, `Stop`, `SubagentStart`,+ `SubagentStop`, and `PreCompact`. Both paths honor `$KIMI_CODE_HOME`.+ Handoff injection happens at `SessionStart` through hook stdout, which Kimi+ Code appends to the model context; `setup-agent` and `uninstall` handle the+ new agent like the other first-class integrations. The `install-mcp` entry+ points at `/mcp?flavor=moonshot`: the Moonshot API validates tool parameter+ schemas against a restricted dialect ("moonshot flavored json schema") that+ rejects root-level `anyOf`/`oneOf`/`allOf` combinators — including the+ `anyOf` on `memory_read_page` — and fails the whole session at `tools/list`.+ Requests carrying that flavor receive flat tool schemas from the server;+ every other client keeps receiving the upstream schemas unchanged.+ `uninstall` matches the Kimi Code entry in either URL form, so removing an+ install made before or after this change both work with the default+ `--mcp-url`.- Grok Build CLI is now a first-class MCP client as well as a hook agent:`install-mcp --client grok` renders and `--apply` merges a native HTTPentry into `$GROK_HOME/config.toml` (default `~/.grok/config.toml`)