httm
Interactive, file-level Time Machine-like tool for ZFS/btrfs/nilfs2 (and even Time Machine and Restic backups!)
Could not verifysource: GitHubhomepageRustMPL-2.0commit 52e9d9c82d92
Rust, MPL-2.0 licensed. The project labels itself: btrfs, btrfs snapshots, cli, command line, command line tool, freebsd, homelab and linux.
Argusic could not get httm running. An Argusic agent installed it in 4.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
httm 0.51.0 builds and runs on Rust 1.99.0; the binary prints its version, help text, and debug config correctly, but requires ZFS/BTRFS/NILFS2 snapshots for data output
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.
- Install time
- 4 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo build --release exited 0; ./target/release/httm --version returned 'httm 0.51.0'; ./target/release/httm --help printed full usage; cargo test exited 0 (0 tests run); --debug output confirmed correct config parsing and filesystem detection
- Model tokens used
- 38,935
- Exact commit tested
- 52e9d9c82d92
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
-rwxrwxr-x 2 runner runner 41M Oct 6 13:23 ./target/release/httm All work is complete. Here's the summary: **Install:** Rust was not present initially. Installed via `rustup`, then `cargo build` succeeded f… **Launch:** `./target/debug/httm --version` prints `httm 0.51.0`, `--help` prints full usage. `--de… **Errors:** None. There were no build errors, no runtime crashes, and no missing dependencies. The … **Verification:** `httm` is a snapshot-aware CLI tool that requires ZFS/BTRFS/NILFS2 snapshots or R… exec /bin/sh -lc "cat << 'EOF' EOF" in /work/repo succeeded in 0ms: tokens used 38,935
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
- Installed in 4.2 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MPL-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.02 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.01 |
Topics (from GitHub)
btrfsbtrfs-snapshotsclicommand-linecommand-line-toolfreebsdhomelablinuxnilfsresticrustshellterminalunixunix-commandunix-shellzfszfs-snapshotszfsonrootzsh
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/httm)Questions
- Does httm run?
- Argusic could not verify that httm runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test httm?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 52e9d9c82d92. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test httm?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does httm take to install?
- 4.2 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 httm need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing httm?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for httm?
- 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.