Labsco
Labsco/Plugins/heygen-com/hyperframes
PLUGIN / HEYGEN-COM

HeyGen HyperFrames

Turns “make me a video” into markup and an MP4 — HeyGen's video engine, handed to a coding assistant as working instructions.

COMMUNITY★ 33.3k GitHub starsApache-2.0Read the official docs ↗

Labsco Summary

ShowHide
Why a video here gets written as code rather than laid out in an editor, which starting point sends a request down which route, which pieces can be opened alone when one layer of a video misbehaves, and at what point a HeyGen account starts to matter.

A video that is really a web page.

A HyperFrames video is an HTML file. Elements carry their own start times and durations, animation sits on a timeline that can be scrubbed to any point, and the renderer steps through that file frame by frame in headless Chrome before encoding the result with FFmpeg — so the same input gives back the same video.

Worth knowing before anything else: the assistant is writing a web page, not driving a timeline editor.

What you bring decides the route.

One skill is meant to be read before the rest. It takes the request as it arrives and routes it, mostly on what is already in hand:

  • A product or marketing page, or just a brief — a launch piece.
  • A topic with no product and no footage behind it — a narrated explainer whose visuals are all invented.
  • A GitHub pull request, read through the gh command-line tool — a walkthrough of what changed.
  • A music track — something cut to its beats.
  • A recording of a person speaking — subtitles, or broadcast-style overlay cards.
  • A Remotion project — rebuilt here, one way only.
  • Nothing in particular — a deck, a short motion graphic, or a freeform piece worked out in conversation.

The parts every route leans on.

Under those routes sit the parts every one of them draws on, and any can be loaded by itself:

  • The rules a file has to obey before it will render at all, and the motion vocabulary on top of them — including the seven animation runtimes it can drive, with GSAP as the default.
  • The choices taken before building: palette, lettering, narration, the beat the thing is cut to.
  • The supply side: visual blocks to install rather than write, music and images found or generated, a design carried over from Figma.
  • The terminal tool that walks a project from empty folder to finished file.

Where it renders, and where it reaches.

The render runs on the machine it was started from; that same terminal tool can hand it to AWS Lambda instead.

The media step is the part that goes outward: it looks in the project first, then in a shared local store, and only then searches HeyGen's own hosted media, freezing whatever it finds into the project so the file cannot shift under a finished video. Reaching that hosted side is where an account on HeyGen's end comes into it.

What gets installed: 19 skills

Skills

The front door, and the only one intended to be loaded before anyone knows what is being asked for. It takes a video request in whatever words it turns up in, works out which route that request actually is, and names the lower pieces the route will need.

hyperframesHyperFrames builds videos out of web pages; this is the front desk you start at, which works out what you are really asking for and hands the job to the right part of the system.