brag
You built it. Now brag. Turn the project you just created into a short, shareable launch video with one command.
Runssource: GitHubPythonMITcommit c893c5ed52ae
Python, MIT licensed.
brag runs. An Argusic agent installed it in 14 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Repo check scripts pass, all 5 example brag videos are valid MP4s, 5 music tracks are valid MP3s, Hyperframes CLI renders test compositions successfully, and the docs site serves content on port 8080.
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 100 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.
- Hyperframes browser ensure download hung on progress spinner3 minutes
- sharp module failed via npx (glibc/ABI mismatch on cached binary)2 minutes
- unzip not available and no root for apt install2 minutes
- Hyperframes doctor still reported Chrome missing after cache placement2 minutes
- Node.js v18.19.1 too old for Hyperframes (needs >=22)1 minute
- Install time
- 14 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npx hyperframes render in tmp test composition completed in 17.8s producing a valid 10s 30fps MP4 (verified by ffmpeg -v error -i). node scripts/check-brag-slim.mjs passed (files in sync), node scripts/check-docs.mjs passed (3 gallery videos, all refs exist). Docs http server returned 200 with hero+gallery content.
- Model tokens used
- 208,776
- Exact commit tested
- c893c5ed52ae
- 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.
exec /bin/sh -lc 'echo "Scripts passed and Hyperframes render succeeded."' in /work/repo succeeded in 0ms: Scripts passed and Hyperframes render succeeded. exec /bin/sh -lc 'export PATH="/tmp/node-v22.14.0-linux-x64/bin:$PATH" && npx --yes hyperframes doctor 2… exited 1 in 787ms: 0 2026-09-27T13:30:30.295872Z ERROR codex_core::session: failed to record rollout items: thread 01a0e… tokens used 208,776 2026-09-27T13:30:30.298162Z ERROR codex_core::session: failed to record rollout items: thread 01a0e…
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 MIT, as reported by its host.
What did not, or is not known
- Took 14 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 12 Python projects Argusic has installed and timed, brag was the 11th fastest to reach a running state, and 7 of 12 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.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/brag)Questions
- Does brag run?
- Yes. brag runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test brag?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c893c5ed52ae. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test brag?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does brag take to install?
- 14 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 brag need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing brag?
- 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 brag compare with the alternatives?
- Of the 12 Python projects Argusic has installed and timed, brag was the 11th fastest to reach a running state, and 7 of 12 reached one at all.
- Where is the evidence for brag?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.