Agent loop in under a minute
From rough brief and optional media inputs through setup, research, storyboard/design updates, image cues, build, render, and review.
The CLI is the agent workflow layer.
VibeFrame turns a written brief into STORYBOARD.md and DESIGN.md and then routes asset generation, scene composition, build reports, render inspection, and final MP4 export through commands any bash-capable coding agent can run.
# Brief → project files → generated assets → MP4# brief.md can be messy notes; media/ can hold your filesmkdir -p launch/mediavibe setup --scope projectvibe init launch --from brief.md --json# Agent researches the topic, then edits STORYBOARD.md + DESIGN.mdvibe storyboard validate launch --jsonvibe plan launch --jsonvibe build launch --dry-run --max-cost 5 --jsonvibe build launch --max-cost 5 --jsonvibe status project launch --refresh --jsonvibe inspect project launch --jsonvibe render launch -o renders/final.mp4 --jsonvibe inspect render launch --cheap --json✓ review-report.json ready for the next agent pass
brief.md can be rough notes, pasted research, links, or a one-line idea. Optional photos, logos, screenshots, clips, or voice files can live in media/. A coding agent then edits STORYBOARD.md and DESIGN.md, runs the build, reviews the reports, and renders the MP4.
From rough brief and optional media inputs through setup, research, storyboard/design updates, image cues, build, render, and review.
The shareable MP4 from the storyboard-driven build path, without exposing the whole process.
Primary path: rough brief, optional media, setup, init, storyboard/design, generated assets, composition, render.
Escape hatch: ask for one standalone image, video, narration, music, or motion asset.
Escape hatch: change existing media with captions, reframe, highlights, overlays, BGM, cleanup.
Use a rough brief and optional media/ inputs first. Lower-level media, scene, timeline, and YAML commands stay available when an agent needs to debug a specific stage.
curl -fsSL https://vibeframe.ai/install.sh | bashAdds the vibe CLI.
vibe setup --scope projectWrites ./.vibeframe/config.yaml for this workspace.
vibe init launch --from brief.md --jsonReads rough brief.md. Optional source files live in launch/media/.
vibe build launch --dry-run --max-cost 5 --jsonShows missing cues, provider needs, estimated cost, and planned assets.
vibe build launch --json && vibe render launch --json && vibe inspect render launch --cheap --jsonWrites reports agents can inspect, repair, and re-render.
Primary path: BUILD from storyboard via vibe build. Existing-media workflows still use vibe remix, edit, and audio.
Agents can reason from structured files and JSON reports instead of guessing which UI state changed.
# Create a project from intentvibe init my-video --from "45-second launch video" --json✓ STORYBOARD.md + DESIGN.md created# Validate, plan, and dry-run before spendingvibe storyboard validate my-video --jsonvibe plan my-video --jsonvibe build my-video --dry-run --max-cost 5 --json✓ build-report.json includes cost and missing cues# Build, review, repair, rendervibe build my-video --max-cost 5 --jsonvibe status project my-video --refresh --jsonvibe inspect project my-video --jsonvibe scene repair my-video --jsonvibe render my-video -o renders/final.mp4 --jsonvibe inspect render my-video --cheap --json✓ final.mp4 + review-report.json
Describe the video. Your coding agent edits project files, callsvibewith JSON output, then uses reports for the next pass.
vibe init launch --from brief.md --json && vibe build launch --dry-run --jsonvibe storyboard revise launch --from "stronger hook" --dry-run --jsonvibe scene repair launch --json && vibe render launch --json && vibe inspect render launch --cheap --jsonvibe doctor auto-detects six host families today and vibe init scaffolds the right project file for each.
Anyone running another bash-capable agent gets the universalAGENTS.mdfallback.
vibe context and guidesAgents can load the project rules, JSON envelope shape, public command surface, and step-by-step guides directly from the CLI.
Load agent rules, JSON envelope conventions, project files, and report locations.
Scene authoring — STORYBOARD.md → composed video via vibe build and vibe render.
Expose the small first-run command set before an agent searches the full catalog.
vibe guide # list available topicsvibe schema --list --surface public --json # compact command catalogvibe guide scene --json # structured workflow for an agent hostGuides are plain CLI commands, so they work the same from a terminal, Codex, Claude Code, Cursor, Aider, Gemini CLI, OpenCode, or any other host that can run shell commands.
82 tools for Claude Desktop, Cursor, OpenCode, or Claude Code. MCP is optional; use it when your host prefers typed JSON-RPC tool calls over shell commands.
In Claude Desktop:
"Load the scene guide, build the storyboard project in demo-video, then render the final MP4"
Claude Code, Codex, Cursor, and other coding agents can drive vibe directly through shell commands and project guidance files. Run vibe agent only when you want a standalone natural-language session inside the CLI.
'Build this storyboard into a launch video' — when no host agent is available
OpenAI, Claude, Gemini, xAI Grok, OpenRouter, Ollama — swap with -p flag
Project files, build reports, generation, media, export, filesystem
Useful when no external coding agent or MCP host is available
The storyboard project loop is the default. Use YAML when you need a reproducible multi-step workflow with budget guards, checkpoints, and step references.
name:asset-pipelinesteps:- id:backdropaction:generate-imageprompt:"modern tech studio"- id:videoaction:generate-videoimage:$backdrop.output# reference- id:narrationaction:generate-ttstext:"Start with a storyboard."output:assets/narration.mp3
vibe run promo.yaml --dry-runvibe run promo.yaml --resumeStart with the storyboard build. Drop into primitives only when an agent needs one asset, one edit, or one reproducible pipeline.
vibe build my-video --jsonSTORYBOARD.md + DESIGN.md to assets, scenes, reports
vibe run pipeline.yamlDeclarative YAML pipelines, --resume + budget guards
vibe remix highlightsLong video → AI analysis → best moments
vibe remix animated-captionWord-by-word TikTok/Reels-style captions
vibe remix auto-shortsLong video → vertical shorts with captions
vibe audio dubTranscribe → translate → TTS in any language
MIT licensed · v0.106.0 · project files, JSON reports, terminal commands, YAML, and MCP workflows.