mac-cleaner-cli
Free macOS CLI to clean disk space, caches, logs, Homebrew, Xcode. Open-source alternative to CleanMyMac
Runssource: GitHubhomepageTypeScriptMITcommit 9bc7c61b6418
TypeScript, MIT licensed. The project labels itself: cache, cache cleaner, cleanup, cli, developer tools, disk cleaner, disk space and free disk space.
mac-cleaner-cli runs. An Argusic agent installed it in 5 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Installation and build succeed with pnpm + Node 22. All 344 tests pass across 40 files. CLI runs correctly: --version (1.3.5), --help prints full usage, scan finds cleanable files, categories lists all categories.
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.
- npm 9.2.0 resolver bug: Cannot read properties of null (reading 'edgesOut')2 minutes
- Node v18.19.1 below required >=20.12.0 and project is os=darwin only1 minute
- rolldown native binding missing for linux-x64-gnu (wasm32-wasi fallback fails)1 minute
- Node 20 styleText API doesn't accept array of style names (needed Node 22+)1 minute
- @inquirer/core not found at runtime (transitive dep not linked into pnpm store root by default)0.5 minutes
- Test execSync calls 'bun src/index.ts' but bun unavailable0.5 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- pnpm run test: 40 test files, 344 passed; node dist/index.mjs --version returned '1.3.5'; node dist/index.mjs --help listed all 7 commands with options; node dist/index.mjs scan found 167.4 MB cleanable (25 items); node dist/index.mjs categories listed all 17 categories in 5 groups
- Model tokens used
- 91,037
- Exact commit tested
- 9bc7c61b6418
- 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.
/bin/sh -lc 'cd /work/repo && PATH="$HOME/.local/node22/bin:$HOME/.local/share/pnpm/bin:$PATH" node…
const { execSync } = require('"'child_process');
const out = execSync('pnpm run test 2>&1', {cwd: '/work/repo', encoding: 'utf8', max_output: 100000…
const lines = out.toString();
const tf = lines.match(/Test Files\\s+(\\d+) passed/);
const tpass = lines.match(/Tests\\s+(\\d+) passed/);
console.log('TF:', tf?.[1], 'TPASS:', tpass?.[1]);
\" 2>&1" in /work/repo
succeeded in 2286ms:
TF: 40 TPASS: 344
tokens used
91,037Replay 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 5 minutes.
- Recovered from all 6 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 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.
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 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)
cachecache-cleanercleanupclideveloper-toolsdisk-cleanerdisk-spacefree-disk-spacehomebrewjunk-cleanerlog-cleanermacmac-utilitiesmacosmacos-cleanernodejsopen-sourcesystem-cleanuptypescriptxcode
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mac-cleaner-cli)Questions
- Does mac-cleaner-cli run?
- Yes. mac-cleaner-cli runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test mac-cleaner-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9bc7c61b6418. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mac-cleaner-cli?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mac-cleaner-cli take to install?
- 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 mac-cleaner-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mac-cleaner-cli?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for mac-cleaner-cli?
- 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.