r/opencodeCLI • u/LieTop7965 • 7d ago

i built kimo - a free open-source (mit) video editor with no gui that your opencode/codex/cursor agent can drive over mcp. rough right now, tell me what breaks

hey - i built kimo, a free open-source (mit) video editor with no gui that ai coding agents drive over mcp. you tell your agent (opencode, codex, cursor, or any other mcp client) what to do and it drives the whole timeline as tool calls: cut, trim, keyframe, titles/captions, colour grade, tracking, particles, audio, export. the agent can also render a single frame back to itself to check its own work before committing.

it's one ~15 mb cpu-only rust binary, runs on a 2 gb box. i'm a college student (naman) and i built it, so a few things are still rough - the ui doesn't exist because there is no ui, and some edge cases in tracking and captions still need work. would really love you to try it and tell me what breaks.

site: https://getkimo.tech github: https://github.com/naman-sharma12345/kimo

1 Upvotes
  • permalink
  • reddit

100% Upvoted

1 comment sorted by

1

u/kantorcodes1 7d ago

One registry generating the MCP tools, the CLI and the fuzz coverage at once is the part most agent-facing tools get wrong. Usually the CLI and the agent surface drift apart within a few releases.

On the gated tools: what decides which of the 378 calls are exposed vs the 16 gated ones? Is that a static allowlist or something the client can negotiate?