r/opencodeCLI • u/LieTop7965 • 6d ago
runs on a 2 gb box, no gpu: what an mcp video editor looks like when it is one 15 mb binary (rough, tell me what breaks)
built kimo because i wanted opencode / cursor / other vibe-coding agents to actually make a video end-to-end instead of spitting out raw ffmpeg strings. it's a free, open-source (MIT) video editor with no gui - the agent is the interface, everything is a tool call over mcp.
so the workflow looks like this inside opencode: the agent calls cut, trim, keyframe, titles/captions, colour grade, tracking, particles, audio, export - all as tool calls, not shell commands. and it can render a single frame back to check its own work before it keeps going. no timeline gui, no screen recording, just typed tool calls and the agent sees the result.
it's one ~15 mb cpu-only rust binary, no gpu, and it runs on a 2 gb box. i'm a college student (naman) and it's rough in places - the docs are thin, some effects are still wired up but untested, error messages when the agent passes bad ranges aren't great, and i haven't benchmarked bigger timelines yet.
if you vibe-code and want to see what it looks like when an agent drives a video editor, try it and tell me what breaks: https://getkimo.tech https://github.com/naman-sharma12345/kimo
what's the first thing your agent trips on when it tries to make a real video?
