Skip to content

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 security/wiki-symlink-confinement

AkitaOnRails55736b786bf3
diff --cc CHANGELOG.md
index fa369d6a,a76064fb..b74f5839
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -12,9 -12,31 +12,34 @@@ and this project adheres to [Semantic V
provider. (#1026)
### Fixed
-- Fixed Codex on the Kimi coding endpoint failing every model call with
- "tools.function.parameters is not a valid moonshot flavored json schema
- (... detected infinite recursion without termination condition ...)".
- Moonshot's validator never resolves `$ref`, so the `$defs`/`$ref` pairs
- Codex forwards from MCP input schemas failed the request at any depth —
- including the `ReasoningTier` reference on `memory_query` and
- `memory_explore` and the `FeedbackKind` reference on `memory_feedback` —
- not just at the root. The `?flavor=moonshot` dialect now inlines every
- `#/$defs/*` reference and drops the emptied `$defs` table; nested
- combinators (which Moonshot accepts) and runtime validation are unchanged.
- `?flavor=bedrock` and `?flavor=gemini` keep serving `$defs`/`$ref` as
- before. (#1093)
+ - Fixed generic OpenCode commands selecting integration contracts from command
+ spelling instead of the executable's major version. `run opencode` now probes
+ the exact executable once and carries the resolved V1/V2 dialect through
+ session discovery, launch, auto-wire, and transcript import; hook and MCP
+ installers use the same strict resolver, while container-oriented
+ `setup-agent` requires an explicit V1/V2 artifact dialect. Probe and launch
+ share one captured child environment with `--env` overlays, including Windows
+ key casing. Automatic launch skips an unresolvable OpenCode candidate without
+ hiding other harnesses. Hook/MCP transitions reuse ownership-verified endpoint
+ and token settings across both schemas and reject conflicting generated
+ entries. Migrations remove only entries proven generated by ai-memory, and plugin
+ cleanup never overwrites a concurrent user replacement while restoring an
+ unowned quarantined file. (#1097)
++- Fixed Codex on the Kimi coding endpoint failing every model call with
++ "tools.function.parameters is not a valid moonshot flavored json schema
++ (... detected infinite recursion without termination condition ...)".
++ Moonshot's validator never resolves `$ref`, so the `$defs`/`$ref` pairs
++ Codex forwards from MCP input schemas failed the request at any depth —
++ including the `ReasoningTier` reference on `memory_query` and
++ `memory_explore` and the `FeedbackKind` reference on `memory_feedback` —
++ not just at the root. The `?flavor=moonshot` dialect now inlines every
++ `#/$defs/*` reference and drops the emptied `$defs` table; nested
++ combinators (which Moonshot accepts) and runtime validation are unchanged.
++ `?flavor=bedrock` and `?flavor=gemini` keep serving `$defs`/`$ref` as
++ before. (#1093)
+- Confined wiki reads, writes, indexing, recovery, and lifecycle cleanup to real
+ project-tree directories by refusing symbolic links and filesystem reparse
+ points at namespace roots or descendants. (#1107)
- Fixed `memory_handoff_list` MCP tool calls being counted under writes in
`client_activity`: the read-only inspection tool is now classified as a read
in `tool_call_is_write`. (#1088)