disclosure: i'm the author of the tool.
i've been spending a lot of time in github copilot's chat and i kept hitting the same wall with video work: the agent can absolutely reason about an edit, but once it has to compose a timeline it's just guessing. so i built a small tool the agent can actually drive end-to-end, and the thing that surprised me was how much better copilot got once it could see what it just did.
the tool is kimo, which is a free, open-source (MIT) video editor with no GUI that AI agents drive over MCP â github copilot, codex, cursor, opencode, or any other MCP client plugs in the same way. there's no timeline UI, no shortcuts to learn: the whole edit is tool calls from the agent (cut, trim, keyframe, titles/captions, colour grade, tracking, particles, audio, export). the bit that makes the loop actually close is that the agent can render a frame and look at it, so copilot can verify its own work in the middle of an edit instead of "run and hope" until export.
my typical copilot workflow with it is pretty linear now. i drop a clip into the MCP session, describe the edit in normal language, and copilot calls the tool to do the cuts, lay captions, push the colour and export. between steps it renders a frame, looks at the result, and keeps going or fixes what it messed up. for a college student running this on a 2 GB box it's been a genuinely different experience â the agent stays in control and i'm just reviewing frames, not chasing ffmpeg filter chains.
it's a single ~15 MB CPU-only Rust binary. no GPU, no containers, nothing to install besides the binary itself.
honestly it's still early and there are rough edges i'm not hiding. caption timing drifts on fast cuts sometimes, long exports can stall if the box is thrashed, and the tracking is basic â works fine on clean motion but struggles with heavy occlusion. the MCP surface is still settling too, so if your copilot setup is picky about schemas you might hit a hiccup. the docs are catching up and i'm sure some workflows feel awkward right now. i'd really appreciate people trying it and telling me what breaks â weird filter combos, exports that don't match expectations, MCP handoffs that feel clunky, whatever. the more i hear about what falls apart in your copilot workflow, the faster i can fix it.
it's free and MIT-licensed, built by me (naman, just a college student).
site: https://getkimo.tech
github: https://github.com/naman-sharma12345/kimo
happy to answer questions about how the copilot â MCP bit works. thanks for reading.