Render-time, post-hoc warning: when the slowest RenderChunk Lambda invocation burned through more than 80% of the 900-second cap, surface a warning at the end of --wait mode pointing at --max-parallel-chunks. The cost-analysis sweep hit this twice — inspector-launch at 1080p/60 and 4K@anything blew past the cap with default 16-way fan-out, producing a Sandbox.Timedout retry storm. The next user to push fps or duration on a heavy composition will hit the same wall; this turns a cryptic SFN failure into a one-line hint they can act on before the next render. Plumbing: - getRenderProgress tracks max billed-duration across RenderChunk invocations (the only state whose runtime is gated by the 15-min cap; Plan + Assemble are off-path). - RenderProgress.maxChunkDurationMs is null before the first chunk reports back. - LAMBDA_TIMEOUT_MS / CHUNK_RUNTIME_WARN_RATIO / CHUNK_RUNTIME_WARN_MS live in chunkRuntime.ts and are exported from the SDK so external callers (custom CLIs, monitoring) can match the threshold. - CLI's render --wait path prints the warning with a suggested --max-parallel-chunks value scaled by the observed headroom ratio. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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 running at http://localhost:3002
npx hyperframes preview --port 4567
render
Render a composition to MP4:
npx hyperframes render ./my-composition.html -o output.mp4
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
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