agent-hud-open
A HUD for Claude Code, Codex and 25 more coding agents. Know your quotas, tokens and sessions at a glance, answer requests and jump back in one click. On Mac, Windows and Linux, your phone and your watch.
Runssource: GitHubhomepageRustApache-2.0commit c6d41101012a
Rust, Apache-2.0 licensed. The project labels itself: ai agents, claude code, codex, coding agents, cursor, deepseek, developer tools and github copilot.
agent-hud-open runs. An Argusic agent installed it in 55 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Rust engine binary builds in debug and release modes, responds correctly to JSON-lines snapshot and system RPCs, and 731 Rust test groups pass with zero failures; installer tests pass 7/7; all TypeScript packages typecheck; desktop Tauri build is blocked on Linux by missing system-dev packages (glib, webkit2gtk, soup) that require root to install.
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.
- libglib2.0-dev system package not installed (`glib-2.0.pc` not found by pkg-config), blocking desktop/Tauri build on Linux (cargo fails on glib-sys build dependency)10 minutes
- MCP host-tools tests fail 6/6 because `bun` is not in PATH (spawnSync bun ENOENT)5 minutes
- `.ts` test files in packages cannot run on Node 18 (need Node 22+ for native --experimental-run-ts); 13 app tests and 1 engine-client test skipped3 minutes
- Install time
- 55 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo test --workspace (selective packages) returned all 'test result: ok', 731 test groups with 0 failures; echo '{"id":1,"method":"system","params":{}}' | timeout 3 target/release/agent-hud-engine returned valid JSON with 2 top-level keys; installer tests 7/7 passed
- Model tokens used
- 85,097
- Exact commit tested
- c6d41101012a
- 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.
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s Now I have a comprehensive picture. Let me prepare the final result. exec /bin/sh -lc 'export PATH="$HOME/.cargo/bin:$HOME/.local/bin:$PATH" && cd /work/repo && du -sh targe… succeeded in 0ms: 23M target/release/agent-hud-engine 203M target/debug/agent-hud-engine Here is the final report. tokens used 85,097 Here is the final report.
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 3 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.
What did not, or is not known
- Took 55 minutes to install, slower than the median of the 121 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 122 ai-agents projects Argusic has installed and timed, agent-hud-open was the 117th fastest to reach a running state, and 94 of 122 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)
ai-agentsclaude-codecodexcoding-agentscursordeepseekdeveloper-toolsgithub-copilotgrokhudlinuxmacosmcpnotchopencoderusttauritoken-usagevibe-codingwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/agent-hud-open)Questions
- Does agent-hud-open run?
- Yes. agent-hud-open runs. Argusic installed and launched it on a clean machine in 55 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test agent-hud-open?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c6d41101012a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test agent-hud-open?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does agent-hud-open take to install?
- 55 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 agent-hud-open need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing agent-hud-open?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does agent-hud-open compare with the alternatives?
- Of the 122 ai-agents projects Argusic has installed and timed, agent-hud-open was the 117th fastest to reach a running state, and 94 of 122 reached one at all.
- Where is the evidence for agent-hud-open?
- 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.