hyperframes
Write HTML. Render video. Built for agents.
Runssource: GitHubTypeScriptApache-2.0commit 61ba800a5db0
TypeScript, Apache-2.0 licensed. The project labels itself: ai, animation, ffmpeg, framework, gsap, html, mcp and puppeteer.
hyperframes runs. An Argusic agent installed it in 74 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
HyperFrames monorepo builds and tests with 9,800+ passing tests. CLI binary works (version 0.8.20, init scaffolds projects, lint validates). Two test failures are environmental: lsof not available (1 CLI test), and worker_threads .ts loading under vitest (7 producer tests).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 98.1 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18 provided, project requires v22+2 minutes
- bun not installed1 minute
- SDK package.json exports pointed import to .ts sources, breaking Vite/Node resolution1 minute
- lsof not available: CLI portUtils test reports the self-reported PID instead of the OS-confirmed PID
- Producer shader transition worker pool tests fail: Node worker_threads cannot load .ts worker files under vitest -- all 7 failures have the same root cause
- Install time
- 74 minutes
- Cold machine to finish
- 69 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- node ./packages/cli/dist/cli.js --version returned '0.8.20'; node ./packages/cli/dist/cli.js init /tmp/test-hf-video --example blank scaffolded a project; npx hyperframes lint on that project reported 0 errors, 0 warnings. All packages built with bun run build (exit 0). Full test suite: CLI 2860 passed/1 failed/3 skipped (portUtils lsof gap), lint 534 passed, parsers 928 passed, player 362 passed, core ~400+ passed, producer 614 passed/7 failed (worker .ts gap), studio 4591 passed/1 skipped, shader-transitions 12 passed, sdk-playground 3 passed, studio-server 37 passed
- Model tokens used
- 778,676
- Exact commit tested
- 61ba800a5db0
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- 7 Producer tests: Node worker_threads can't import `.ts` files without a tsx loader registered … - **CLI binary works**: `hyperframes --version` returns `0.8.20`, `hyperframes init --example blank… tokens used 778,676 Now I have all the data. Let me compile the final ARGUSIC_RESULT. **Key findings:** - **Build succeeded** for all packages after installing Node 22 and fixing the SDK's `package.json`… - **Tests**: ~9,800 tests across all packages, with 9 failures that are environmental: - 1 CLI test: `lsof` not available in the container (OS PID verification can't work) - 1 SDK Playground test: timed out under resource contention (passes individually) - 7 Producer tests: Node worker_threads can't import `.ts` files without a tsx loader registered … - **CLI binary works**: `hyperframes --version` returns `0.8.20`, `hyperframes init --example blank…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 74 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 ai projects Argusic has installed and timed, hyperframes was the 37th fastest to reach a running state, and 30 of 37 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
aianimationffmpegframeworkgsaphtmlmcppuppeteerrenderingtypescriptvideo
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hyperframes)Questions
- Does hyperframes run?
- Yes. hyperframes runs. Argusic installed and launched it on a clean machine in 74 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test hyperframes?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 61ba800a5db0. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test hyperframes?
- The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hyperframes take to install?
- 74 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does hyperframes need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hyperframes?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does hyperframes compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, hyperframes was the 37th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for hyperframes?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.