funzzy
Gives developers and coding agents one reliable edit loop
Runssource: GitHubRustMITcommit a229380a3d4d
Rust, MIT licensed. The project labels itself: agentic coding, ai agents, ai tools, cli, developer tools, dx, file watcher and harness engineering.
funzzy runs. An Argusic agent installed it in 1.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.
All 931 unit tests pass, both funzzy and fzz debug/release binaries build and run correctly, config validation and schema output work as documented.
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.
- Two flaky tests failed due to coarse filesystem mtime granularity (the test wrote a file then checked for mtime change within the same clock tick)0.2 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- `cargo test` exited 0 with 931 passed, 0 failed; `target/debug/funzzy --version` returned 'funzzy 2.0.0'; `target/debug/funzzy check` returned 'config valid: 5 job(s), 3 in parallel group(s), concurrency 2'
- Model tokens used
- 178,808
- Exact commit tested
- a229380a3d4d
- 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 58695ms:
test result: ok. 931 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 5.15s
exec
/bin/sh -lc '. "$HOME/.cargo/env" && cd /work/repo && cargo build --release 2>&1 | tail -3' in /wor…
succeeded in 39941ms:
Compiling glob v0.3.4
Compiling funzzy v2.0.0 (/work/repo)
Finished `release` profile [optimized] target(s) in 40.08s
All good. Here's my final report:
tokens used
178,808
All good. Here's my 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.
- Installed in 1.5 minutes, faster than the median of the 29 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 30 agentic-coding projects Argusic has installed and timed, funzzy was the 10th fastest to reach a running state, and 23 of 30 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 1.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
Topics (from GitHub)
agentic-codingai-agentsai-toolsclideveloper-toolsdxfile-watcherharness-engineeringrusttoolsunit-testingunixwatchwatcher
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/funzzy)Questions
- Does funzzy run?
- Yes. funzzy runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test funzzy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a229380a3d4d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test funzzy?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does funzzy take to install?
- 1.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 funzzy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing funzzy?
- 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 funzzy compare with the alternatives?
- Of the 30 agentic-coding projects Argusic has installed and timed, funzzy was the 10th fastest to reach a running state, and 23 of 30 reached one at all.
- Where is the evidence for funzzy?
- 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.