Frontier video generation for coding agentsv0.115.2

Let your agent generate video
under a ceiling it cannot cross.

Your keys. Your bill. Your limit.

VibeFrame gives Claude Code, Codex, or Cursor the commands to plan a video, generate the assets from Seedance, Runway, Veo, and Kling on your own provider keys, and render a finished MP4. Every paid step sits behind a dry run and a hard --max-cost ceiling, and every failure comes back as machine-readable recovery actions instead of a stack trace.

the spend gate

# price the whole build first - no provider call, no key needed
vibe build film --dry-run --max-cost 3 --json
{
  "success": false,
  "error": "Estimated cost $10.93 exceeds --max-cost $3.00.",
  "code": "COST_CAP_EXCEEDED",
  "exitCode": 1,
  "retryWith": [
    "vibe build . --stage all --skip-backdrop --json",
    "vibe build . --stage all --max-cost 10.93 --json"
  ],
  "recoverable": true,
  "data": { "plan": { "estimatedCostUsd": 10.93 } }
}
# stderr, exit 1 - the agent stops instead of guessing

Intent

STORYBOARD.md

Beats, narration, cues

Design

DESIGN.md

Palette, type, motion

Build

build-report.json

What it cost, where it stopped

Review

review-report.json

What is wrong, who fixes it

$curl -fsSL https://vibeframe.ai/install.sh | bash

No API key needed to try it - the whole pipeline runs locally for $0.

View on GitHub Watch the render Claude Desktop extension

Desktop extension: open the downloaded .mcpb, pick a workspace folder, done - no terminal needed.

What it produces

Generated end to end by `vibe build`.

1080p, four scenes, one consistent character. Here is how it was made.

Directed AI video

Flagship render - one character, many scenes

Chasing Light - one photographer across a single arctic night

Trek, first aurora, the whole sky, dawn - the same character throughout. Character sheet → image storyboard → image-to-video → composed render, generated end-to-end by vibe build.

From install to MP4

Five commands, start to finish.

brief.md can be rough notes, pasted research, links, or a one-line idea, and optional photos, logos, clips, or voice files live in media/. Your coding agent edits STORYBOARD.md and DESIGN.md, runs the build, reads the reports, and renders. Scene composition itself runs on Hyperframes.

1. Install · global

curl -fsSL https://vibeframe.ai/install.sh | bash

Adds the vibe CLI. No API keys needed yet.

2. Draft · project files

vibe init launch --from brief.md --json

Reads rough brief.md. Optional source files live in launch/media/.

3. Price · before any spend

vibe build launch --dry-run --max-cost 12 --json

Costs nothing and needs no key. Prints the estimate and names the keys each stage would need.

4. Generate · under the cap

vibe setup --scope project && vibe build launch --max-cost 12 --json

BYO-key generation on Seedance, Runway, Veo, or Kling. Over the ceiling it refuses and hands back recovery actions.

5. Render · review

vibe render launch --json && vibe inspect render launch --cheap --json

Chrome + FFmpeg render, free. Writes reports agents can inspect, repair, and re-render.

No provider account yet? Step 4 has a $0 variant: vibe build launch --tts kokoro --skip-backdrop --json swaps paid generation for local Kokoro narration and agent-authored HTML scenes. Steps 1, 2 and 5 are unchanged, and step 3 has nothing left to price.

Use with your AI agent

Works with the agent you have

Describe the video in Codex, Claude, Cursor, or a terminal. Your host agent edits project files, callsvibewith JSON output, then uses reports for the next pass.

vibe init

Writes one AGENTS.md (plus CLAUDE.md, which just imports it). That is the whole contract - Codex, Cursor, Aider, Gemini CLI, OpenCode and any other bash-capable agent read the same file.

vibe host setup --write

Adds typed MCP tools for the three hosts that support them: .mcp.json, .codex/config.toml, .cursor/mcp.json. Optional - the CLI works without it.

vibe doctor reports which hosts it detects, and vibe host doctor all --json verifies what landed.

MCP Ready

77 tools for Claude Desktop, Cursor, Claude Code, and Codex project configs. MCP is optional; use it when your host prefers typed JSON-RPC tool calls over shell commands.

In Claude Desktop:

"Dry-run the build in demo-video, then generate under a $10 cap and render the final MP4"

initstoryboard_validateplanbuildinspect_projectscene_repair+71 more tools

Primary path and escape hatches

Start with the priced build: dry-run first, generate under the cap. Drop into primitives only when an agent needs one asset, one edit, or one reproducible pipeline.

Build Under a Cap

vibe build my-video --max-cost 12 --json

STORYBOARD.md + DESIGN.md to generated assets, scenes, reports - refuses over the ceiling

Frontier Generation

vibe generate video

One clip on Seedance, Runway, Veo, or Kling - your keys, dry-run priced

Auto Highlights + Shorts

vibe remix highlights

Long video → best moments, or vertical shorts with captions

Captions + Dub

vibe remix animated-caption

Word-by-word captions, or transcribe → translate → TTS with vibe audio dub

Video as Code

vibe run promo.yaml --dry-run

Declarative YAML pipelines with budget guards, checkpoints, and --resume

Review + Repair

vibe inspect render --cheap

Machine-readable review with nextActions and deterministic repair

Open source frontier video generation for coding agents.

MIT licensed · v0.115.2 · your keys, your bill, your ceiling - CLI, MCP tools, JSON reports, and recovery contracts.

Star on GitHub Read the docs

Let your agent generate videounder a ceiling it cannot cross.

Generated end to end by vibe build.