VibeFrame: video generation for agents
VibeFrame
A CLI and MCP server: an agent makes video from a brief on your Seedance, Runway, Veo and Kling keys under a hard spend cap
- 185 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Generation runs on your own provider keys and costs money, while the `--max-cost` ceiling applies only when set
- Keys are saved in `~/.vibeframe/config.yaml` and the installer runs a script from the network
Install
- Works in
Manual install
curl -fsSL https://vibeframe.ai/install.sh | bashThen `vibe doctor`. Needs Node.js 20+, FFmpeg and Chrome. The installer downloads and runs a script, so read it first.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Generation runs on your own provider keys and costs money, while the `--max-cost` ceiling applies only when set
- Keys are saved in `~/.vibeframe/config.yaml` and the installer runs a script from the network
This is third-party code. Review the repository files before installing.
What it does
VibeFrame turns a written brief into a plan, generates assets with frontier models (Seedance, Runway, Kling, Gemini Omni) and renders a finished MP4. It runs as the `vibe` CLI for Claude Code, Codex, Cursor and any agent with shell access, and as an MCP server for clients that prefer typed calls. The core idea is that the price is known up front. `vibe build film --dry-run --max-cost 3 --json` computes an estimate without calling providers or needing keys. If the estimate exceeds the ceiling, the build refuses to start: the agent gets a `COST_CAP_EXCEEDED` code and `retryWith` options, cheaper ones included. Every failure arrives machine-readable, not as a stack trace. After `vibe init` a project consists of `STORYBOARD.md`, `DESIGN.md` and scenes in `scenes/`, one Markdown file per scene. The files can be edited by hand or by an agent. Assembly and rendering run locally through FFmpeg and Chrome, and VibeFrame delegates scene composition to Remotion and Hyperframes. Paid generation is needed only for images and video, while Kokoro narration and assembly work without keys.
Who it is for. Developers and marketers who hand video work to Claude Code or Codex and want a spending ceiling the agent cannot get around.
Good fit when
- A video is needed from notes or a single line and the agent should build the plan, scenes and render itself
- Generation cost must be known before paying, including when you do not have keys yet
- One character runs through several scenes and the shots have to match in look
- An agent iterates on variants and every refusal should come with ready steps to retry
- Video is built without paid keys: Kokoro, HTML scenes, Chrome and FFmpeg
Not a fit when
- The job is only HTML scenes and rendering them: the authors themselves advise using Hyperframes directly
- You only need to edit ready files without generation: FFmpeg is enough
- The machine has no Node.js 20, FFmpeg and Chrome: `vibe doctor` will not pass without them
Example request
Make a 30-second launch video from brief.md. First compute the estimate with a 5 dollar ceiling and show it; start generating only after my answer.Limitations
Node.js 20 or newer, FFmpeg and Chrome or Chromium are required; `vibe doctor` checks them. The `--max-cost` ceiling works only when it is set, so put the limit into the command or the project config.
Keys are needed for the providers you use: `OPENAI_API_KEY`, `FAL_API_KEY`, `GOOGLE_API_KEY`, `RUNWAY_API_SECRET`, `KLING_API_KEY`. The package is called `@vibeframe/cli`, and `npx vibeframe` would run an unrelated package with the same name.
The project is not affiliated with HeyGen. The `curl | bash` installer puts the CLI into the XDG data directory. The repository's last commit is from November 2026.
How to disable. Remove the `vibeframe` entry from the MCP client config and the install directory in `~/.local/share/vibeframe`. Keys sit in `~/.vibeframe/config.yaml`; delete them there.
FAQ
How do I cap video generation spending?
Add `--max-cost` to the command: `vibe build launch --max-cost 5`. The build refuses to start if the estimate is higher. `--dry-run` computes the estimate without keys.
How do I connect the VibeFrame MCP server?
`vibe host setup cursor --write` writes `.cursor/mcp.json`, and `vibe host setup all` prints snippets for every client. By hand, add a server with the command `npx` and the arguments `-y @vibeframe/mcp-server`. Claude Desktop has a ready extension, `vibeframe.mcpb`.
Can I build video without paid keys?
Yes, the local half is free: Kokoro narration, HTML and CSS scenes, headless Chrome and FFmpeg. Keys are only needed for generating images and video with provider models.
Which generation models are supported?
From the README: Seedance, Runway, Kling and Gemini Omni, and the repository description also names Veo. Providers and models are tracked in `MODELS.md`.
What if the build refuses on cost?
The agent gets a `COST_CAP_EXCEEDED` code and a `retryWith` list: for example skip the backdrop with `--skip-backdrop` or raise the ceiling to the estimate. Raise the ceiling only with your consent.
Discussion
No questions or reviews yet.
Related
CLI toolsSkills, a CLI and an MCP server that let Claude Code or Codex make video from a brief: editing, graphics, voiceover, subtitles
A skill turns a topic or script into a drawn explainer through a brief, storyboard, sample segment and local rendering.
Two skills for generative video and images: video writes Seedance, Kling and Veo prompts by dramaturgy rules, image picks the model and its syntax
Vibe Vision Video is a video skill that keeps the project editable so its author or another agent can continue working on it.
A local video studio for your coding agent: describe a video in one sentence, the agent directs, your machine renders with no cloud
A skill that makes your agent film a short product video: concept, edit, sound and render on Remotion or HyperFrames
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| VibeFrame: video generation for agents (this card) | no | 185 | |
| HyperFrames | no | 79,556 | an HTML scene engine without paid generation or cost estimates |
| video-use | no | 30,591 | a video editing skill for agents without a budget ceiling |
README in short
The README opens with a cost-refusal example, then explains where VibeFrame sits relative to Remotion and Hyperframes: it delegates composition and takes on paid generation itself. Installation, the scene-based project structure, character continuity across shots and MCP setup follow.