kimo is an MCP-based AI video editor made with Rust and C++. The repository description states that it exposes every editing operation as a tool that AI can call. The 2026-11-01 commit 7ff6238 is a documentation-only change that touched a single file, README.md (19 lines added, 17 lines removed). The commit message is "README: v8 release", and the heading of the release section in the README changed from the v6.0.0 section to a v8 section. The file names listed in the download table also changed from 6.0.0 to 8.3.0, and the SHA256SUMS link was fixed to point to the v8.3.0 release tag.
The v6 feature list was replaced with outro music, match_shot_look, volume normalization applied only to dialogue segments, a Ken Burns push-in on static b-roll, a smarter punch-in that splits long dialogue takes, face-aware captions that move subtitles according to face position, a zoom blur wipe on b-roll transitions, and a montage mode. The montage mode filters out blurry, dark, or shaky segments via best_segments, beat_sync_montage cuts to the music's beat and adjusts shot length according to music energy, and montage_color_match matches the color between clips. The README adds that this mode is for video without spoken dialogue. The MCP badge also changed from 452 tools to 526 tools, and the body explains that the 526 registered tools belong to 14 groups.
However, since this commit changes not engine code but just a single README page, the evidence that the new features actually work remains confined to the README description for now. The tool counts are also inconsistent with each other. Although the number of registered tools was raised to 526, what is stated to work in the default build is 438, and what is blocked by feature gates is 16 when OCIO and mesh import are combined. Even adding 438 and 16 does not reach 526. The README itself states that only four clients — Claude Code, Codex, Cursor, OpenCode — have been confirmed on a documentation basis, and that on Windows only the configuration format was checked and nothing was executed. The full list of changes has been left to CHANGELOG.md, so what exactly v8 changed and how far it goes still has to be checked in the release notes.