OrkasVideoStudio

What does this agent do, and when should you use it?

OrkasVideoStudio is an MIT-licensed, local-first toolkit that lets any coding agent capable of running a shell or speaking MCP — Claude Code, Codex, Cursor — drive video composition, generation, and editing. It is not a black-box video agent: a video is expressed as a readable, diffable, re-renderable plan.json IR where editing one line re-renders only that segment. The project ships three capability lines — Compose (HTML motion graphics to MP4), Edit (cut, trim-silence, subtitle burn-in, dubbing, localization), and Generate (BYO keys for image/video/TTS providers) — plus an automatic end-to-end Auto pipeline orchestrated via stage-plan and stage-assemble. The zero-key trunk builds on HyperFrames 0.7.60, ffmpeg, and whisper.cpp, while generation uses your own OpenAI, Gemini, Doubao, or other keys. Originally the built-in video agent inside the Orkas desktop app, it was extracted into an agent-agnostic toolkit exposed through the ovs CLI and an MCP server.

The agent first reads the video-router skill to lock a production line, then reads the stage skills (stage-plan, stage-compose, video-craft), authors composition-manifest. and plan.json, and runs deterministic operations: ovs composition prepare / ovs draft / ovs render produce HyperFrames-based HTML motion-graphic output; the ovs edit family (probe, trim, concat, burnsubs, overlay, loudness, mix, trim-silence, remove-fillers) processes supplied footage; ovs transcribe plus silence, scenes, and quality use whisper.cpp and ffmpeg to analyze material and select highlights; ovs speak, image, and video call BYO-key providers for narration and footage; and ovs plan validate / promise-check act as a delivery guard verifying the finished cut keeps its promise (real motion, not a silent slideshow) before shipping. Generate segments have ratio, duration, and operation checked against the configured video.provider, and the MuAPI adapter only accepts validated Kling v2.1 endpoints.

1. A content creator wants Claude Code to produce a 60-second vertical explainer on vector databases with Chinese voiceover and captions — the Compose line handles HTML motion-graphic scenes, narration synthesis, and burned-in captions.
2. An editor needs to turn a one-hour screen recording into three 30-second captioned highlight clips — the Edit line uses scenes/quality to locate good parts, rank-takes to choose, and trim-silence to tighten.
3. A product manager wants an English voiceover, subtitles, and normalized loudness added to product-demo.mp4 — the Edit chain runs transcribe, localize, speak, mix, burnsubs, and a loudness pass.
4. A podcaster wants silences and 'um's removed from a webcam take — the Edit line performs deterministic jump-cutting with an auditable evidence trail.
5. A short-video team needs a 15-second 9:16 promo with a generated opener, composed feature callouts, and one voiceover — the Auto line weaves generate + compose + narration in a single plan.json guarded before delivery.
6. An indie developer wants a 5-second cinematic city-at-dawn shot generated in Cursor with their own OpenAI/Gemini/Doubao keys — the Generate line calls their own provider keys with no managed backend.

How do you install or deploy this agent?

Prerequisites: Node >= 22, and ffmpeg + ffprobe on your PATH. The npm packages are being published; for now install from source:

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
alias ovs="node $PWD/packages/cli/dist/index.js"  # optional

Once published: npm i -g @orkas/video-studio, then run ovs doctor. Generation (image/video/TTS) is opt-in and requires your own keys configured in ~/.config/orkas-video-studio/config.json or environment variables such as OVS_IMAGE_API_KEY, OVS_VIDEO_API_KEY, and OVS_TTS_API_KEY.

How do you use this agent?

Three ways to hook it up, whichever your agent supports:
1) Native skills: ovs skills --install --target claude (installs to ~/.claude/skills; add --scope repo for ./.claude/skills); use --target codex for Codex (installs to ~/.agents/skills).
2) MCP server: claude mcp add ovs -- npx -y @orkas/video-studio-mcp (from source: point it at node <repo>/packages/mcp/dist/index.js).
3) Self-describing CLI: any shell-capable agent can run ovs skills to list skills, ovs skill video-router to print full instructions, and ovs --help for the full command surface.
Typical session: the agent reads video-router to lock the line, authors composition-manifest. and plan.json, runs ovs composition prepare and ovs draft composition --out draft.mp4 --report draft-report.json, then verifies with ovs plan promise-check plan.json before returning the cut.

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?