Studio & tools

HyperFrames Studio — HTML-to-video on the canvas

HyperFrames Studio is a local HTML-to-video composer that runs on your PC and opens as a locked widget on the VibeFuse canvas. You write compositions as HTML, preview them in Studio, then render MP4s into a shared renders folder. Jarvis can inspect the current project folder, compose scenes, check, preview, and render — then drop a Video widget to play the file.

Local Studio Port 4567 C:\vibefuse\hyperframes Jarvis compose + render

What HyperFrames Studio is

Studio is not a cloud render farm and not a separate desktop app you install by hand. VibeFuse owns the process: it binds the workspace root, serves the Studio UI at http://127.0.0.1:4567, and embeds that UI in the built-in HyperFrames widget. You stay on the canvas — next to terminals, browsers, and Jarvis — while a composition becomes an MP4.

Node.js 20+ must be on PATH. Without it, Start Studio fails and the status pill stays on error. The marketing overview lives on the HyperFrames landing page; this page is the in-app reference.

Settings → Local Servers → HyperFrames

Open the gear in the title bar and go to Settings → Local Servers. The HyperFrames card sits with Piper, Whisper, Skill Seekers, and Crawl4AI + SearXNG. Voice devices stay on Settings → Voice; MCP connections stay on Settings → Extensions. This card is only Studio: enable, workspace, port, chips, buttons, and status.

The Local Servers tab as a whole is documented on /docs/local-servers.

Toggle — Enable HyperFrames Studio

Enable HyperFrames Studio is the master switch on the card. Off means Studio is not allowed to run: the status pill reads disabled, Start Studio does nothing useful, and Jarvis tools that need Studio report it as off. On means VibeFuse may start Studio — it still does not spawn the process until you click Start Studio or Jarvis hits a HyperFrames tool.

Enabling the toggle is not the same as starting Studio. Flip the switch, then Start Studio (or ask Jarvis to compose / open the widget).

Workspace and Studio port

Workspace: C:\vibefuse\hyperframes
Studio port: 4567
Studio URL: http://127.0.0.1:4567
Renders: C:\vibefuse\hyperframes\renders

The workspace field on the card is read-only. Keep projects under that root so the Studio Renders tab and Jarvis tools see the same tree. Sibling compositions share one renders\ folder at the workspace root — finished MP4s are copied there instead of hiding in a nested studio directory.

Studio binds localhost only. Do not expose port 4567 to the internet.

Permission chips

The card shows capability chips so you can see what this local Studio is allowed to do. They are not extra Settings tabs — they describe the Studio surface Jarvis and the widget use:

Chip	What it covers
Studio UI	The locked webview at `http://127.0.0.1:4567` inside the HyperFrames widget
Init	Scaffold a blank project under the workspace (`hyperframes_init`)
Catalog	List compositions and registry items (`hyperframes_list` / `hyperframes_run` catalog)
Preview	Local preview of the current composition
Check	Validate the composition before you spend a render
Render	Write an MP4 into `renders\`
Capture	Capture / snapshot frames from Studio
Media	Local media the composition reads (assets under the workspace)

Buttons — Start Studio, Restart, Stop, Open widget

Button	What it does
Start Studio	Starts the local Studio process and waits until `http://127.0.0.1:4567` is healthy. Requires Enable HyperFrames Studio and Node.js 20+.
Restart	Stops the process and starts it again against the same workspace. Use after a hung preview or a stuck connecting pill.
Stop	Shuts Studio down. The widget shows a wait / retry panel until you start it again.
Open widget	Places the built-in HyperFrames widget on the active session canvas and loads the locked Studio webview. Starts Studio first if it is not running.

Jarvis can do the same open path with hyperframes_open or create_hyperframes_widget — see Jarvis tools.

Status pills

Pill	Meaning
ready	Studio is up. The widget can load `http://127.0.0.1:4567`. Jarvis tools that need a live Studio will succeed.
connecting	The process was asked to start and VibeFuse is waiting for the port. The widget shows Starting….
error	Start failed or Studio died. Common causes: Node.js missing, port 4567 taken, workspace unreadable. Use Retry on the widget or Restart on the card.
disabled	Enable HyperFrames Studio is off. Flip the toggle before Start Studio or any Jarvis tool.

Canvas widget — HyperFrames (`com.vibefuse.hyperframes`)

HyperFrames is a built-in widget. You cannot remove it from Settings → Widgets. Its id is com.vibefuse.hyperframes. The window is a locked Studio webview: no address bar, no free browsing. It only shows Studio (or the wait panel while Studio is starting / down).

Spawn it from the Widgets rail, from Open widget on the Local Servers card, or by asking Jarvis to open HyperFrames.
While Studio is connecting, the widget shows HyperFrames Studio — Starting…. On error, Retry appears.
Once ready, you get the Studio UI bound to C:\vibefuse\hyperframes so the Renders tab lists the shared renders\ folder.

Treat it like the YouTube widget: a purpose-built locked viewer, not a Browser widget you can point anywhere.

Renders, then the Video widget

hyperframes_render writes an MP4 into C:\vibefuse\hyperframes\renders. The Studio Renders tab lists that same folder. To play the file on the canvas, spawn the built-in Video widget (com.vibefuse.video) — Jarvis does this with create_video_widget and a path.

Video is a local player for those MP4s (and other local media). It is not Studio. Compose and render in HyperFrames; watch in Video.

Jarvis tools

Jarvis (wake word, hold-to-talk, or the Jarvis chat widget) calls these tools. Ask in plain language — “make a 20-second title card about this repo” — and Jarvis picks the sequence. The full catalog is on /docs/jarvis-tools.

Tool	What it does
`hyperframes_status`	Studio state, `studioUrl`, workspace dir, active session folder
`hyperframes_open`	Start Studio if needed and focus / open the HyperFrames widget
`create_hyperframes_widget`	Place the HyperFrames widget on the active session canvas
`hyperframes_compose`	Required before render — writes a visible composition from the prompt and workspace. Skipping this yields a black MP4
`hyperframes_init`	Scaffold a blank project under `C:\vibefuse\hyperframes`. Always compose after init
`hyperframes_list`	List compositions / projects in the HyperFrames workspace
`hyperframes_inspect_workspace`	File tree plus README / package.json so the video is about the folder you have open
`hyperframes_write`	Write a file inside the HyperFrames directory only
`hyperframes_read`	Read a file inside the HyperFrames directory only
`hyperframes_run`	CLI verbs: catalog, check, preview, lint, and other HyperFrames commands
`hyperframes_render`	Render an MP4 into `C:\vibefuse\hyperframes\renders`
`create_video_widget`	Play the rendered MP4 (or another local video path) on the canvas

Bundled skills such as hyperframes-core, hyperframes-animation, hyperframes-creative, hyperframes-cli, and media-use sit in the Skills rail so Claude, Codex, and Cursor widgets follow the same composition contract.

Compose, then render

Enable HyperFrames Studio on Settings → Local Servers.
Click Start Studio or ask Jarvis to open HyperFrames (first tool use starts it).
Point Jarvis at the project: it should call hyperframes_inspect_workspace when the film is about the current folder.
hyperframes_compose writes scenes from your prompt. Do not skip this.
Optional: hyperframes_run with check / preview / catalog, or edit files with hyperframes_write / hyperframes_read.
hyperframes_render writes the MP4 into C:\vibefuse\hyperframes\renders.
create_video_widget plays it on the canvas.

Init alone is a blank starter. Always compose before render or the MP4 is black.

Studio does not auto-start on launch

VibeFuse does not start HyperFrames when the app opens, even if Enable HyperFrames Studio is on. That keeps launch light and leaves port 4567 free until you need it.

Start Studio on the Local Servers card — manual, immediately.
Open widget — starts Studio if it is down, then places the widget.
First Jarvis tool use — hyperframes_open, hyperframes_compose, hyperframes_render, and the other HyperFrames tools start Studio when it is enabled and not already running.

Troubleshooting

Symptom	Fix
Pill stays disabled	Turn on Enable HyperFrames Studio in Settings → Local Servers → HyperFrames.
Studio will not start / error	Install Node.js 20+ on PATH. Click Start Studio again. Confirm nothing else is bound to port 4567.
Widget stuck on Starting…	Wait for connecting to become ready, or Restart. Retry on the wait panel if error is showing.
Renders tab is empty after a successful render	Confirm the file landed in `C:\vibefuse\hyperframes\renders`, not a nested project folder. Refresh Studio.
Black MP4	Run `hyperframes_compose` (or compose in the Studio UI) before `hyperframes_render`.
Jarvis says Studio is off	Enable the toggle, then Start Studio or ask again so the first tool use can start it.

FAQ

Does Studio start when VibeFuse launches?

No. Even with Enable HyperFrames Studio on, the process stays down until you click Start Studio or Jarvis uses a HyperFrames tool.

Where do MP4s land?

C:\vibefuse\hyperframes\renders — the same folder the Studio Renders tab lists. Play them with the Video widget or create_video_widget.

Why is the render a black video?

hyperframes_init is a blank starter. Call hyperframes_compose (or compose in Studio) before hyperframes_render.

Can I point the widget at another URL?

No. com.vibefuse.hyperframes is a locked Studio webview on http://127.0.0.1:4567. Use a Browser widget if you need a free URL bar.