* fix(cli): audio and media-use print control characters from project files as visible escapes hyperframes audio, audio --read and media-use resolve (including --candidates) printed file names, element ids, transcript words, model descriptions and media manifest fields as they were. They now pass through terminalText, so a control character shows as a visible \xNN escape. The media-use engine runs without the CLI's packages, so it carries a small copy of the helper. --json output is unchanged. * fix(engine): playlist check refuses drive-relative and other colon-prefixed entries ffmpeg reads an HLS or ffconcat entry with a colon before its first separator as a URL or a drive, and opens it apart from the list's folder. The folder check read entries such as C:Videos\a.mp4 or c:x.mp4 as names inside the folder and approved them. It now refuses any entry, raw or percent-decoded, whose colon comes before its first /, \, ? or #, as it already refuses absolute and parent-folder paths. http and https segments are still kept. * fix(cli): background-removal and Kokoro TTS model files are pinned to a sha256 The u2net_human_seg weights and the Kokoro model and voices files were downloaded from release URLs and used whatever bytes arrived, and any cached copy was trusted because it existed. Each file now has a pinned size and sha256. A cached copy is checked before it is loaded and downloaded again when it does not match. A download that does not match is discarded with a message that names the file. * fix(engine): playlist check reads entries from the folder ffmpeg uses ffmpeg resolves a list's entries against its path cut at the first ? or #. A list at proj/h#z/list.m3u8 naming ../h#z/x.ts was judged against proj/h#z and approved, while ffmpeg opened proj/../h#z/x.ts. Entries are now judged against the same cut folder. A list in a folder such as "Take #2" still passes when its entries resolve inside that folder. * fix(cli): a pinned model's cached copy is checked and removed under the download lock ensurePinnedFile removed a cached copy that failed its check before the download lock was taken, so a concurrent run could delete a file another run had just published. downloadFile now takes a keepExisting check and runs it under the lock: a copy that passes is kept, one that fails is removed and downloaded again. The mismatch error now says the file does not match its expected checksum, and that a retry helps only if the download was interrupted or corrupted. * fix(cli): audio escapes each field's line breaks, and media-use escapes recipe and stats output The audio formatters escaped their output line by line, so a newline inside a src, warning or transcript still printed as a real line break. Each output line is now escaped whole with terminalText, which shows a newline inside a field as \x0a. media-use resolve also escapes its recipe lines and its --stats lines, which print recipe names, paths and missed intents. * fix(cli): media-use error messages show control characters as visible escapes resolve printed error messages as they were, and some name project or cache data, such as the known recipe names when a recipe is not found. Every error: line now passes through terminalText, as the success lines already do. * ci: the edit accuracy filter includes the CLI model file check The CLI's pinned model download now imports whisper/modelFile.ts, so a change to it must run the edit accuracy bench too. * test(cli): pinned model tests use private temp folders and rename like downloadFile The tests wrote fixtures under fixed names in the shared temp folder, and their download stand-in checked for a file before replacing it. Each test now works in its own mkdtemp folder, and the stand-in asks keepExisting directly and renames the part file into place, as downloadFile does. * test(cli): the media-use terminalText copy is checked against core's The media-use engine keeps its own copy of terminalText. A CLI test now compares the two over U+0000 to U+00A0, so a change to either fails until both match. keepsDest moves above downloadFile's doc comment, which belongs to downloadFile.
hyperframes
CLI for creating, previewing, and rendering HTML video compositions.
Install
npm install -g hyperframes
Or use directly with npx:
npx hyperframes <command>
Requirements: Node.js >= 22, FFmpeg
Commands
init
Scaffold a new Hyperframes project from a template:
npx hyperframes init my-video
cd my-video
preview
Start the live preview studio in your browser:
npx hyperframes preview
# Studio: http://localhost:3002/#project/my-video
# Server: http://localhost:3002
npx hyperframes preview --port 4567
In an interactive terminal, the preview stays attached until you press
Ctrl+C. In a non-interactive shell such as a coding-agent session, the same
command starts a managed preview that survives after the command returns. Use
--background or --foreground to choose explicitly, and manage persistent
previews with --status, --stop, --list, and --kill-all. Add --json to
managed lifecycle commands for machine-readable output. --foreground --json
prints the ready-session envelope once, then remains attached until stopped.
audio
Measure where sounds land: onsets, the moment each sound peaks, loudness and silence. Give files, or query the film's own clips in film time:
npx hyperframes audio sfx/whoosh.mp3
npx hyperframes audio --at 12 --json
normalize-audio
Measure two local authored audio clips with integrated LUFS and match the target
to the unchanged reference. The command is a dry run unless --write is passed:
npx hyperframes normalize-audio --reference target-audio --target user-audio
npx hyperframes normalize-audio --reference target-audio --target user-audio --write
It updates only the target element's data-volume. Where a full match would pass
Studio's +12 dB ceiling or -1.5 dBTP, it applies the most that fits and says how far
under the reference that leaves the target.
render
Render a composition to MP4. Run from the project directory; the positional
argument is the project directory (not a file), so render the project's
index.html directly, or point at a specific composition file with -c:
npx hyperframes render -o output.mp4
npx hyperframes render -c ./my-composition.html -o output.mp4
A render stops when the process that started it exits. To keep one running after
its launcher exits, set HYPERFRAMES_RENDER_DETACHED=1 and start it in its own
process group, e.g. bash -c 'set -m; HYPERFRAMES_RENDER_DETACHED=1 npx hyperframes render -o out.mp4 < /dev/null > render.log 2>&1 &'.
Piped, non-quiet renders emit a single @hf-diagnostic JSON line when an audio
failure reaches the CLI error handler. Version 1 has operation: "render" and
at most 16 audioFailures: allowlisted stage, reason, owner, retryable, and
optional subprocess exit code, signal, termination reason and OS code. It omits
messages, stderr, source paths/URLs, element IDs and command arguments. Consumers
must ignore unknown versions and fields. This is local CLI output; uploading it
requires the caller's existing consent and privacy checks. Quiet mode (including
batch JSON mode) emits no diagnostic line.
This covers audio preparation and mix failures, including the typed external interruption path. Probe failures retain their existing stage/reason but do not gain subprocess evidence here; browser/FX failures remain classified as internal. Desktop ingestion and live report delivery are separate changes.
Piped, non-quiet renders also emit a single @hf-result JSON line after a local
render succeeds, never after a failure. Version 1 has operation: "render" and
reference_background, the background the render measured from the composition's
root and body: {"kind":"solid","rgb":[r,g,b]}, {"kind":"none"},
{"kind":"unsupported_non_solid"} or {"kind":"unknown"}. A render that applied
motion blur also carries motion_blur: tier ("capture" or "filter", absent
when none ran), movers, failed_frames and a fingerprint of 14 snake_case
counts (absent when the page produced none); it is absent when the render has no
blur summary. Consumers must ignore unknown versions and fields. A --docker render prints no result line from the
launcher. In batch mode each manifest row carries the same reference_background value (null until the row completes, and for a
row that failed).
publish
Upload a project directory and get a hosted URL that keeps working after the CLI exits. Published projects are private by default:
npx hyperframes publish
npx hyperframes publish ./my-video
npx hyperframes publish --public
npx hyperframes publish --yes
Signed-out publishing returns an authentication-required claim URL; opening it
lets someone sign in and claim the project. Sign in first with
npx hyperframes auth login to publish an owned project you can update. Use
--public to make the claimed project visible to anyone. --yes only skips the
confirmation prompt and does not change visibility.
Signed-in publishers can use --update <url-or-id> to target an existing project
or --space <space-id> to publish into a shared team space. If the requested
project is missing or inaccessible, publishing can create a new project instead;
check the printed URL and status.
See the publish reference for all options, including video proxy settings.
lint
Validate your Hyperframes HTML:
npx hyperframes lint ./my-composition
npx hyperframes lint ./my-composition --json # JSON output for CI/tooling
npx hyperframes lint ./my-composition --verbose # Include info-level findings
By default only errors and warnings are shown. Use --verbose to also display informational findings (e.g., external script dependency notices). Use --json for machine-readable output with errorCount, warningCount, infoCount, and a findings array.
compositions
List compositions found in the current project:
npx hyperframes compositions
benchmark
Run rendering benchmarks:
npx hyperframes benchmark ./my-composition.html
doctor
Check your environment for required dependencies (Chrome, FFmpeg, Node.js):
npx hyperframes doctor
browser
Manage the bundled Chrome/Chromium installation:
npx hyperframes browser
info
Print version and environment info:
npx hyperframes info
docs
Open the documentation in your browser:
npx hyperframes docs
upgrade
Check for updates and show upgrade instructions:
npx hyperframes upgrade
npx hyperframes upgrade --check --json # machine-readable for agents
update
Check the CLI and the installed skills for updates in one call, or install both:
npx hyperframes update --check --json # report only, machine-readable for agents
npx hyperframes update --yes # upgrade the CLI, then refresh the skills
Documentation
Full documentation: hyperframes.heygen.com/packages/cli
Related packages
@hyperframes/core— types, parsers, frame adapters@hyperframes/engine— rendering engine@hyperframes/producer— render pipeline@hyperframes/studio— composition editor UI