Skip to main content
Video Lab is a local automation runtime for Codex, Claude Code, and similar agent environments. It validates and renders HTML compositions into MP4 files with Breeze TTS narration by default. Pass --no-audio when the output should be a video-only MP4. Human users normally interact with it through an agent workflow rather than by authoring project files manually. Everything runs on your machine: compositions, assets, and rendered videos stay local, and only the TTS narration request goes to Breeze.

​
Local requirements

Video Lab uses the runtime bundled with the installed Breeze CLI. Local rendering also needs Node.js, FFmpeg, ffprobe, and Playwright Chromium. On first use the runtime downloads Chromium, so run breeze video doctor once to set up and verify the environment.

​
Login and credits

These local commands run without a Breeze login and do not consume credits:
  • breeze video init — create a project from a template.
  • breeze video capture-url — capture a live web page into the project.
  • breeze video validate — check project files and assets.
  • breeze video inspect — detect visual problems frame by frame.
  • breeze video snapshot — export still frames for review.
  • breeze video doctor — verify local dependencies.
Rendering commands require a logged-in Breeze profile or API key with at least 400 credits because they generate Breeze TTS narration:
  • breeze video render
  • breeze video preflight
A --no-audio render still needs the account gate, but it produces a silent MP4 without calling Breeze TTS.

​
Agent workflow

Use the --no-audio render for visual rehearsal. The final render omits --no-audio, generates narration from script.segments[].text, and fails if TTS cannot complete. inspect reports machine-readable findings — text overflow, elements out of frame, missing images, low readability, covered titles — with the scene, timestamp, and a repair suggestion, so an agent can fix the composition and re-run.

​
Visual safety rules

  • Place text on stable light areas, scrims, or solid panels.
  • Keep core titles, captions, and product details inside safe margins.
  • Do not let moving assets cover titles or body text in their final positions.
  • Use timeline_v1 when frame-by-frame animation matters.