webframe
Run a web page like a program
Runssource: GitHubGoMITcommit 25c24cb61aad
Go, MIT licensed. The project labels itself: cross platform, golang, headless browser and purego.
webframe runs. An Argusic agent installed it in 20 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
webframe builds from source with patched glaze (preferGTK3=true), runs with WebKitGTK 4.1 from deb packages, executes JS pages, reports console output, supports exit codes and scripts.
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. 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.
- WebKitGTK 6.0 requires bubblewrap sandbox which fails (no user namespaces)5 minutes
- 4.1 subprocess binaries not found at hardcoded /usr/lib path5 minutes
- WebKitGTK 6.0 shared libraries not found on system4 minutes
- Go not installed in container2 minutes
- Missing dbus-launch, xdg-dbus-proxy, bubblewrap2 minutes
- Install time
- 20 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- webframe -v printed 0.2-dev; webframe -t 10s examples/hello.html printed Hello, world! exit 0; webframe -t 10s examples/timers.html reported timer/animation rates; webframe -x test_exit.js about:blank exited 42 as requested
- Model tokens used
- 257,879
- Exact commit tested
- 25c24cb61aad
- 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 "ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"install_mi…
echo \"Done\"" in /work/repo
succeeded in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:: not found
Done
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 20, "errors": [{"msg": "Go…
tokens used
257,879Replay 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 20 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 13 cross-platform projects Argusic has installed and timed, webframe was the 8th fastest to reach a running state, and 9 of 13 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/webframe)Questions
- Does webframe run?
- Yes. webframe runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test webframe?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 25c24cb61aad. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test webframe?
- The run that produced this verdict cost $0.77: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does webframe take to install?
- 20 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 webframe need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing webframe?
- 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 webframe compare with the alternatives?
- Of the 13 cross-platform projects Argusic has installed and timed, webframe was the 8th fastest to reach a running state, and 9 of 13 reached one at all.
- Where is the evidence for webframe?
- 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.