codeAgent
CodeAgent is an open-source coding agent that lives in your terminal. It understands your repository, plans multi-step changes, writes and edits files, runs commands and tests, and iterates until the task is done, all with a transparent, extensible tool loop.
Runssource: GitHubPythonMITcommit e48780be5294
Python, MIT licensed. The project labels itself: agent, ai agent, cli, coding agent, context engineering, deepseek, llm and mcp.
codeAgent runs. An Argusic agent installed it in 14 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
CodeAgent v0.1.0 is installed with all 41 Python dependencies in .venv, the 67-item verify regression suite passes, and the app launches showing its banner and version.
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.
- NO_COLOR=1 env var broke Rich ANSI rendering in BridgeConsole.print3 minutes
- pip install uv failed: externally-managed-environment (Debian)1 minute
- uv not found after install1 minute
- Install time
- 14 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- python scripts/verify.py passed 67/67 checks (0 failures, 0 skipped); python main.py --help prints CodeAgent v0.1.0 banner
- Model tokens used
- 65,936
- Exact commit tested
- e48780be5294
- 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 "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
succeeded in 0ms:
Three things were done here:
- **`uv sync`** installed all 41 dependencies in `.venv` (Python 3.12.3, Debian container).
- **One fix applied**: added `no_color=False` in `cli_ui.py` line 182 — the environment had `NO_COL…
- **67/67 verify checks pass**, the app launches and prints `CodeAgent v0.1.0` banner. No API keys …
tokens used
65,936
Three things were done here:
- **`uv sync`** installed all 41 dependencies in `.venv` (Python 3.12.3, Debian container).
- **One fix applied**: added `no_color=False` in `cli_ui.py` line 182 — the environment had `NO_COL…
- **67/67 verify checks pass**, the app launches and prints `CodeAgent v0.1.0` banner. No API keys …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 3 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
- Took 14 minutes to install, slower than the median of the 97 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 98 agent projects Argusic has installed and timed, codeAgent was the 64th fastest to reach a running state, and 67 of 98 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)
agentai-agentclicoding-agentcontext-engineeringdeepseekllmmcppythonterminal
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/codeagent)Questions
- Does codeAgent run?
- Yes. codeAgent runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test codeAgent?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e48780be5294. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test codeAgent?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does codeAgent take to install?
- 14 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 codeAgent need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing codeAgent?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does codeAgent compare with the alternatives?
- Of the 98 agent projects Argusic has installed and timed, codeAgent was the 64th fastest to reach a running state, and 67 of 98 reached one at all.
- Where is the evidence for codeAgent?
- 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.