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 3 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
Hermes WebUI server launches on port 8789, responds with HTTP 200 on /health and /, and 11,844+ automated tests pass with 269 skipped (31 due to missing hermes-agent); 7 pre-existing failures involve Node.js ES module import from smd.min.js and test ordering in sharded runs, none affecting production runtime
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 80 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.
- Test shard 0: test_smd_wrapper_runtime_matches_render_md_emphasis_policy fails because Node.js 18 treats smd.min.js (ES module with `export` syntax) as CommonJS since package.json lacks "type": "module"
- Test shard 2: test_live_prose_rebuild_preserves_markdown_dom and test_live_prose_post_rewind_keeps_tail_word_identity fail from same Node.js ES module import issue
- Test shard 3: 3 test_real_smd_parser_* errors from same Node.js ES module import issue
- Test shard 1: test_lmstudio_has_key_true_via_config_yaml fails in sharded run due to test isolation ordering (passes individually)
- Test shard 2: test_openrouter_group_uses_live_fetch_when_available fails in sharded run due to test isolation ordering (passes individually)
- Install time
- 3 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 5 hit, 0 fixed with no human help
- How the result was proved
- curl http://127.0.0.1:8789/health returned HTTP 200 with {"status":"ok"}; curl http://127.0.0.1:8789/ returned HTTP 200 (221KB HTML with title and login form); 11,844+ tests passed across 4 parallel pytest shards (17,245 collected)
- Model tokens used
- 355,701
- 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.
succeeded in 15612ms: 17245 tests collected in 12.60s All results collected. Let me compile the final report: **Installation**: Runtime deps installed (via `.venv` created by `./scripts/test.sh`). 17,245 tests… **Server**: Launched successfully, HTTP 200 on `/health` and `/` endpoints. **Tests**: 11,844+ passed across all 4 shards, 269 skipped (31 due to missing hermes-agent), 7 pre-… tokens used 355,701 All results collected. Let me compile the final report: **Installation**: Runtime deps installed (via `.venv` created by `./scripts/test.sh`). 17,245 tests… **Server**: Launched successfully, HTTP 200 on `/health` and `/` endpoints. **Tests**: 11,844+ passed across all 4 shards, 269 skipped (31 due to missing hermes-agent), 7 pre-…
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 3 minutes, faster than the median of the 38 comparable projects Argusic has measured.
- 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
- Hit 5 errors during setup, 5 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 39 agent projects Argusic has installed and timed, hermes-webui was the 15th fastest to reach a running state, and 30 of 39 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 3 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 3 minutes, hitting 5 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. One attempt is 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.10: 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?
- 3 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?
- 5 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does hermes-webui compare with the alternatives?
- Of the 39 agent projects Argusic has installed and timed, hermes-webui was the 15th fastest to reach a running state, and 30 of 39 reached one at all.
- Where is the evidence for hermes-webui?
- 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.