Dev-Janitor
Cross-platform desktop app for cleaning development artifacts, managing local developer tools, and checking common environment issues.
Runssource: GitHubhomepageRustMITcommit e06fd6ee7838
Rust, MIT licensed. The project labels itself: ai tools, cleanup, desktop app, developer tools, react, rust and tauri.
Dev-Janitor runs. An Argusic agent installed it in 17 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Node.js 24.0.0, pnpm 11.15.1, Rust 1.97.1 installed; pnpm install + build + tsc lint clean; 39 Rust unit tests pass; 320MB debug binary compiled and launched on virtual display, process stayed alive until timeout
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.
- Missing system -dev packages (glib, gtk, webkit2gtk, etc.) for Tauri desktop build5 minutes
- WebKit subprocess hardcodes /usr/lib/.../WebKitNetworkProcess path4 minutes
- Runtime shared libraries not found at link time (no .so symlinks)3 minutes
- EGL_BAD_PARAMETER from prefix Mesa/EGL libs shadowing system ones2 minutes
- Install time
- 17 minutes
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- pnpm test:rust exited 0 (39/39 passed); binary launched on Xvfb display :99, stayed running 5s (exit 124 from timeout=alive)
- Model tokens used
- 488,340
- Exact commit tested
- e06fd6ee7838
- 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.
- **pnpm install** → 63 packages added, lockfile clean - **pnpm build** (vite + tsc) → 128 modules, output in `dist/` - **pnpm lint** (tsc --noEmit) → clean - **pnpm test:rust** → 39/39 passed on core library - **Binary compiled** → 320MB debug binary at `src-tauri/target/debug/dev-janitor-v2` - **Launch verified** → binary started on Xvfb `:99` and stayed alive until 5s timeout (exit 124 = … **Errors encountered & fixed** (all resolved in 17 min): 1. Missing `-dev` system packages (glib, gtk, webkit2gtk, etc.) → extracted 53+ .deb archives into … 2. Missing runtime `.so` symlinks → added runtime .deb packages 3. WebKit hardcodes `/usr/lib/.../WebKitNetworkProcess` → `LD_PRELOAD` intercepts `posix_spawn`/`fa… 4. EGL display conflict from prefix Mesa libs → isolated prefix libs to a minimal `tmplib` **Limitation**: Launching the GTK webview-based GUI requires `LD_PRELOAD` workaround for WebKit sub…
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 4 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 17 minutes to install, slower than the median of the 26 comparable projects Argusic has measured.
Of the 27 ai-tools projects Argusic has installed and timed, Dev-Janitor was the 25th fastest to reach a running state, and 19 of 27 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dev-janitor)Questions
- Does Dev-Janitor run?
- Yes. Dev-Janitor runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test Dev-Janitor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e06fd6ee7838. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Dev-Janitor?
- 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 Dev-Janitor take to install?
- 17 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 Dev-Janitor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Dev-Janitor?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Dev-Janitor compare with the alternatives?
- Of the 27 ai-tools projects Argusic has installed and timed, Dev-Janitor was the 25th fastest to reach a running state, and 19 of 27 reached one at all.
- Where is the evidence for Dev-Janitor?
- 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.