OrkasVideoStudio：用编程代理制作视频

Turn your coding agent into a video studio: describe a video in plain language, and your agent writes the timeline and produces the file.

OrkasVideoStudio 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. orkas_video_studio.mp4 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. "Add an English voiceover + subtitles to product-demo.mp4 and normalize the loudness." Edit transcribe → localize → speak → mix → burnsubs → loudness pass. "Clean the silences and 'um's out of my webcam take and tighten it." Edit deterministic jump-cut with an auditable evidence trail. "Generate a 5s cinematic shot of a city at dawn for the intro." Generate BYO image/video provider → clip on your timeline. "Make a 15s 9:16 promo from this script: generate the opener, compose the feature callouts, one VO." Auto one plan.json woven across generate + compose + narration, guarded before delivery. Install Prerequisites: Node ≥ 22, and ffmpeg + ffprobe on your PATH (needed for edit / transcribe / local media QA). Compose drafts use a VideoStudio QA gate backed by the pinned HyperFrames 0.7.60 package dependency; npx is only a compatibility fallback. Generation is opt-in and needs your own keys. Early development: the npm packages are being published. Until then, install from source — the ovs CLI works exactly the same. From source (works today) git clone https://github.com/Orkas-AI/Orkas-VideoStudio.git cd Orkas-VideoStudio pnpm install && pnpm build node packages/cli/dist/index.js doctor # verify ffmpeg/ffprobe/node # optionally alias it: alias ovs="node $PWD/packages/cli/dist/index.js" From npm (once published) npm i -g @orkas/video-studio # provides the `ovs` command ovs doctor # checks ffmpeg/ffprobe/node; guides any install Drive it from your coding agent The ovs CLI is the canonical interface; the MCP tools mirror it 1:1. There are three ways an agent picks it up — use whichever your agent supports: 1) Native skills (Claude Code / Codex). Materialize the SKILL.md knowledge pack so the agent discovers it by progressive disclosure: ovs skills --install --target claude # → ~/.claude/skills (add --scope repo for ./.claude/skills) ovs skills --install --target codex # → ~/.agents/skills 2) MCP typed tools. Register the server (mirrors the CLI): claude mcp add ovs -- npx -y @orkas/video-studio-mcp # Claude Code codex mcp add ovs -- npx -y @orkas/video-studio-mcp # Codex # from source (until published): point it at node <repo>/packages/mcp/dist/index.js 3) Self-describing CLI (any agent that can run a shell). No native loader needed: ovs skills # list the skills ovs skill video-router # print a skill's full instructions into context ovs --help # the full command surface How a session flows. The agent reads video-router first (it locks the line), then the relevant stage skills, authors the composition and/or plan.json, runs the deterministic ops, and self-verifies with the delivery guard: You: Make a 60s vertical explainer on vector databases, with a Chinese voiceover. Agent: → reads video-router (locks: compose-primary) → reads stage-plan / stage-compose / video-craft → write