You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changelog
0.7.0 — 2026-09-18
Changed
The built-in kimi agent now drives Kimi Code CLI (@moonshot-ai/kimi-code), the successor to
the legacy Python kimi-cli that 0.6.0 targeted. Both install a kimi executable, but Kimi Code
rejects --quiet and --work-dir. Reviews run in prompt mode with a shipped read-only profile
(lib/agents/kimi-reviewer.md: no Edit or Write tools, read-only sub-agents only), the report is
read from --output-format stream-json, and replies resume the exact session id Kimi prints.
The entry stays opt-in. Users of the legacy CLI can keep the old command with a jury.config.json
override; see docs/configuration.md.
Added
report: "kimi-json" reads the assistant text out of Kimi Code's JSON lines, ignoring tool
results and metadata, and rejects non-JSON or empty output; the console shows the decoded words
while the agent runs. {{packageDir}} in a command names the installed package directory, for
files that ship with it.
Claude, Droid, Antigravity and OpenCode now resume their own review conversation
when replying to verdicts, instead of starting fresh with their findings quoted
back. Eight of eleven agents now resume. Each names an explicit session id —
Claude via an assigned --session-id, the others read from structured output —
so a reply can never land in an unrelated conversation.
Droid and Antigravity are read through their JSON output modes, which is where
each reports its session id. Antigravity's reported status is now checked, so a
run that ends early cannot be read as a sign-off.