heh

A terminal UI to edit bytes by the nibble.

Runssource: GitHubRustMITcommit 89b1e9969506

Rust, MIT licensed. The project labels itself: command line, command line tool, cross platform, hex editor, rust and terminal.

heh runs. An Argusic agent installed it in 0.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The heh hex editor builds, passes 5 unit tests, and launches as a TUI app displaying file contents in hex/ASCII with address labels and 12 data label panels.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
1
last tested
stars
504
forks
18
open issues
11
watchers
4
size
0 MB
created
last push

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.

Time lost to each failure while testing heh, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Terminal narrower than ~10 columns causes arithmetic underflow panic at src/screen.rs:1160.1 minutes
Install time
under a minute
Cold machine to finish
3 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
cargo build exited 0; cargo test: 5 passed, 0 failed; script -q -c 'stty cols 80 rows 24; target/debug/heh /tmp/testfile.bin' rendered the full TUI hex editor showing file content in hex and ASCII panels with all label widgets visible
Model tokens used
88,384
Exact commit tested
89b1e9969506
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.

- **No third-party keys required**: This is a standalone TUI hex editor; no external API keys are n…
2026-10-19T16:19:22.196021Z ERROR codex_core::session: failed to record rollout items: thread 01a15…
2026-10-19T16:19:22.196069Z ERROR codex_core::session: failed to record rollout items: thread 01a15…
tokens used
88,384
All done. Here's the summary:
- **Install**: Rust toolchain was not present. Installed via `rustup`, then `cargo build` succeeded.
- **Build**: `cargo build` completed in 29s with no errors.
- **Tests**: `cargo test` — 5 passed, 0 failed, 0 ignored.
- **Launch**: The binary launched and rendered the full TUI (hex table, ASCII table, address column…
- **Known quirks**: Running with `--help` fails with "Stdout is not a TTY device" (expected for a T…
- **No third-party keys required**: This is a standalone TUI hex editor; no external API keys are n…

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 0.5 minutes, faster than the median of the 6 comparable projects Argusic has measured.
  • Recovered from all 1 error 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

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 7 command-line projects Argusic has installed and timed, heh was the 1st fastest to reach a running state, and 6 of 7 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 0.5 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

command-linecommand-line-toolcross-platformhex-editorrustterminal

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/heh.svg)](https://argusic.com/subject/heh)

Questions

Does heh run?
Yes. heh runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test heh?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 89b1e9969506. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test heh?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does heh take to install?
0.5 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 heh need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing heh?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does heh compare with the alternatives?
Of the 7 command-line projects Argusic has installed and timed, heh was the 1st fastest to reach a running state, and 6 of 7 reached one at all.
Where is the evidence for heh?
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.

Discussion