Clean-Coder-AI
✅2-in-1 AI Developer and Project Manager. AI agents plan an entire project in Todoist and code it task by task.
Runs with mockssource: GitHubhomepagePythonApache-2.0commit 77143dfe5061
Python, Apache-2.0 licensed. The project labels itself: agent, ai, cli, code generation, code writing and coding agents.
Clean-Coder-AI runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8 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 unit tests pass (14/14), all 28 source modules import cleanly, main entry points (manager.py, single_task_coder.py) import without error, and Playwright Chromium browser is installed.
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 92 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.
- 6 unit tests failed due to argument order mismatch: tests called run_script_in_env(script_name, work_dir) but the function signature is run_script_in_env(work_dir, execute_file_name). Also logs_from_running_script mock assertions had wrong argument order.5 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pytest -m 'not integration' returned 14 passed, 1 skipped, 2 deselected
- Model tokens used
- 59,872
- Exact commit tested
- 77143dfe5061
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tokens used 59,872 Everything checks out. Let me compile the final result. Here's what I found and fixed: - **Created venv and installed 99+ packages** from `requirements.txt` — all succeeded. - **Identified 6 failing unit tests** due to the tests passing arguments to `run_script_in_env(scri… - **Fixed all tests**: corrected argument order in test calls and assertions to match the real func… - **Verified all 28 source modules** import cleanly. - **Verified `single_task_coder.py` and `manager.py`** parse and import correctly. - **Installed Playwright Chromium** browser for frontend testing support. - **Integration tests** (`pytest -m integration`) require real LLM API keys — that's expected. **Final test suite result**: `14 passed, 1 skipped, 2 deselected` (the 2 deselected are the integra…
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
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 8 minutes to install, slower than the median of the 137 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 138 agent projects Argusic has installed and timed, Clean-Coder-AI was the 71st fastest to reach a running state, and 92 of 138 reached one at all.
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 | 1/3 | Runs with mocks | 92.00 | 0.06 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/clean-coder-ai)Questions
- Does Clean-Coder-AI run?
- Clean-Coder-AI runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test Clean-Coder-AI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 77143dfe5061. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Clean-Coder-AI?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Clean-Coder-AI take to install?
- 8 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 Clean-Coder-AI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Clean-Coder-AI?
- 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 Clean-Coder-AI compare with the alternatives?
- Of the 138 agent projects Argusic has installed and timed, Clean-Coder-AI was the 71st fastest to reach a running state, and 92 of 138 reached one at all.
- Where is the evidence for Clean-Coder-AI?
- 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.