Orkas-AI/Orkas-VideoStudio

> Drive video composition, generation, and editing — and a fully automatic end-to-end
> pipeline — from your coding agent. Claude Code, Codex, Cursor: any agent that can run a
> shell or speak MCP can use it.
https://github.com/user-attachments/assets/13411470-06da-4f64-9bc1-fa52fe27216b
OrkasVideoStudio is not a black-box video agent. A video is expressed as a readable,
diffable, re-renderable plan (plan.json) that your agent — and you — can edit; change one
line and only that piece re-renders. The agent is the brain; this project ships the
knowledge (what makes a good video, and which production line to take), the
deterministic capabilities (render / edit / transcribe / generate — thin wrappers over
hyperframes, ffmpeg, and whisper.cpp), and
that editable IR.
You talk to your agent in plain language — "make a 60-second vertical explainer on vector
databases with a Chinese voiceover and captions" — and it reads the material, writes the
timeline, and produces the file.
## The four production lines
Three orthogonal capability axes, plus an automatic pipeline that weaves them together:
Compose — script → designed HTML motion graphics → mp4. Explainers, kinetic typography,
lower-thirds, data viz, title cards, transitions. No paid keys.
Edit — cut / join / trim-silence / de-filler / mix / burn-in subtitles / dub / localize
real footage you supply, plus highlight selection over long recordings. No paid keys.
Generate — talking-head or cinematic AI footage and imagery via your own provider
keys (BYO — OpenAI, Gemini, Doubao; no managed backend, no lock-in).
Auto (end-to-end) — when a deliverable needs more than one axis, the agent routes to a
single cross-modal plan.json: stage-plan builds the EDL, stage-assemble walks it and
delegates each segment back to compose / generate / edit, and a deterministic
delivery guard (ovs plan promise-check) verifies the finished cut keeps its promise
(e.g. real motion, not a silent slideshow) before anything ships.
The plan is the contract: "the footage in the middle, generate an opener, compose the stats,
one voiceover over all of it" becomes one editable file where every segment, caption, and
narration line is independently re-renderable.
## Relationship to Orkas
OrkasVideoStudio began life as the built-in video agent inside Orkas —
the AI-team desktop app — where it was validated end-to-end, then extracted into this
agent-agnostic, MIT-licensed toolkit.
Inside Orkas it ships as a built-in agent —
no separate install; the zero-key trunk works out of the box.
Everywhere else you install it into your own coding agent (below) and get the same
capabilities via the ovs CLI and MCP server.
Links: orkas.ai (website) · github.com/Orkas-AI
(open-source projects) · this repo.
## Use cases
Each is a real prompt you'd give your agent; the router picks the line for you.
| You say… | Line | What happens |
| "Make a 60s vertical explainer on what a vector DB is, Chinese voiceover + captions." | Compose | HTML motion-graphic scenes → narration (BYO TTS) → burned-in captions → mp4. |
| "Turn this 1-hour screen recording into three 30s highlight clips with captions." | Edit | scenes/quality find the good parts, rank-takes picks, trim-silence/remove-fillers tighten, subtitles burned in. |