HYPERFRAMES STUDIO

Local HTML-to-Video — HyperFrames on the VibeFuse Canvas

AI video in VibeFuse is not a cloud render farm. HyperFrames Studio starts on your PC, binds C:\vibefuse\hyperframes, and opens as a widget. Ask Vibe Agent to compose a piece about the current project folder, then render an MP4 into renders\ and play it with a Video widget.

Download VibeFuse HyperFrames docs

Agent tools for motion

Compose, don’t render black

hyperframes_compose writes a visible title, tagline, and scene cards from your prompt + workspace. Skipping it produces an empty starter MP4.

Studio on localhost:4567

Start / Restart / Stop from Settings → Local Servers. Open widget drops Studio on the active session.

Workspace-aware videos

hyperframes_inspect_workspace reads README and package.json so the film is about the repo you have open.

Skills on the rail

hyperframes-core, animation, creative, CLI, and media-use skills teach any connected agent the same composition contract.

✓ Local Studio
✓ Agent compose + render
✓ MP4 Video widget
✓ No cloud render bill
✓ Node.js 20+

Run HyperFrames free Full VibeFuse docs

Explore VibeFuse & harness guides

HyperFrames FAQ

What is HyperFrames in VibeFuse?

A local HTML-to-video studio. VibeFuse starts it on 127.0.0.1:4567, stores projects in C:\vibefuse\hyperframes, and can render MP4s for a Video widget.

Can the AI make the video?

Yes. hyperframes_compose builds scenes from your prompt and workspace, then hyperframes_render writes the MP4. Always compose before render or you get a black starter.

Do I need a cloud video API?

No. Studio and renders are local. You need Node.js 20+ on PATH.

Where do MP4s go?

C:\vibefuse\hyperframes\renders — also listed in the Studio Renders tab.