Skip to content
EYAS Docs

Studio

What this is for. Studio is where EYAS runs local production engines — tools that take something the agent wrote (HTML, an EDL) and render a file on this machine. Engines: Hyperframes (HTML→MP4) and Video Use (footage→MP4). Media is the other lane: hosted prompt→pixels (Magnific, Higgsfield, fal). Do not mix them.

Route: /studio. Sidebar: Content → Studio.

When to use it

Section titled “When to use it”
  • You want an agent to write a motion graphic, title card, or explainer as HTML and render a deterministic MP4.
  • You do not want a generative video from a prompt — that is Media.
  • You will add more local engines later; they belong here, not under Media.

Typical workflow

Section titled “Typical workflow”
  1. Open Studio (/studio).
  2. Read the Hyperframes card. Node.js 22+, FFmpeg, and the Hyperframes CLI must be OK (warnings are fine if npx can fill in).
  3. Ask in a conversation. The agent should call hyperframes_status, then hyperframes_create, hyperframes_write, hyperframes_lint, hyperframes_render.
  4. The MP4 lands in Documents and on that chat turn.

Engines

Section titled “Engines”

Each card is one engine. Ready means every blocking check passed. Missing pieces show a remedy — install those, do not expect a silent fallback. Chromium sandbox is never turned off automatically.

See Hyperframes and Video Use for contracts and tools.

Section titled “Related”