hermes-webui
Hermes WebUI: The best way to use Hermes Agent from the web or from your phone!
Runssource: GitHubhomepagePythonMITcommit ff26335b8761
Python, MIT licensed. The project labels itself: agent, ai agents, hermes, hermes agent and nous research.
hermes-webui runs. An Argusic agent installed it in 7 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Hermes WebUI boots from .venv, serves /health (HTTP 200), /api/onboarding/status returns full JSON, and 16893 of 17245 pytest tests pass. The missing Hermes agent (not installed) is the only missing component for full functionality.
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 90 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.
- 6 failures in test_live_prose_fade_cursor_source_space.py due to Node.js v18.19.1 not loading ES module export syntax in static/vendor/smd.min.js
- 1 failure in test_remote_terminal_workspace.py: /etc/ssh path does not exist in this container
- 1 failure in test_streaming_markdown.py: same Node.js ES module loading issue with smd.min.js
- 6 errors in test_smd_media_in_stream.py: same Node.js ES module loading issue with smd.min.js
- Install time
- 7 minutes
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl -sS http://127.0.0.1:8789/health returned {"status":"ok"} and .venv/bin/python -m pytest tests/ -q returned 16893 passed, 338 skipped, 8 failed, 6 errors, 27 subtests passed
- Model tokens used
- 243,224
- Exact commit tested
- ff26335b8761
- 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.
[webui] {"ts": "2026-11-02T23:35:21Z", "remote": "127.0.0.1", "method": "GET", "path": "/health", "…
exec
/bin/sh -lc '# Kill any remaining background processes from earlier
pkill -f "server.py" 2>/dev/null; true' in /work/repo
exited 143 in 0ms:
Now let me produce the final result.
2026-11-02T23:35:50.026342Z ERROR codex_core::session: failed to record rollout items: thread 01a19…
2026-11-02T23:35:50.026471Z ERROR codex_core::session: failed to record rollout items: thread 01a19…
2026-11-02T23:35:50.026484Z ERROR codex_core::session: failed to record rollout items: thread 01a19…
tokens used
243,224
Now let me produce the final result.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.
- Installed in 7 minutes, faster than the median of the 137 comparable projects Argusic has measured.
- Recovered from all 4 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.
- Measured 2 times, so the result is not a one-off.
Of the 138 agent projects Argusic has installed and timed, hermes-webui was the 66th fastest to reach a running state, and 92 of 138 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.
- A quick evaluation: it was running 7 minutes after the clone.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hermes-webui)Questions
- Does hermes-webui run?
- Yes. hermes-webui runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test hermes-webui?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ff26335b8761. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test hermes-webui?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hermes-webui take to install?
- 7 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 hermes-webui need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hermes-webui?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does hermes-webui compare with the alternatives?
- Of the 138 agent projects Argusic has installed and timed, hermes-webui was the 66th fastest to reach a running state, and 92 of 138 reached one at all.
- Where is the evidence for hermes-webui?
- All 2 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.