How did Argusic test building-a-coding-agent-from-scratch-course?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 798a1e7ad07c. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test building-a-coding-agent-from-scratch-course?

The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does building-a-coding-agent-from-scratch-course take to install?

4.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 building-a-coding-agent-from-scratch-course need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing building-a-coding-agent-from-scratch-course?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for building-a-coding-agent-from-scratch-course?

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.

building-a-coding-agent-from-scratch-course

From agent user to agent builder: build a Claude Code-style coding agent from scratch in Python: 8 articles, 4 videos, one codebase

Runssource: GitHubPythonApache-2.0commit 798a1e7ad07c

Python, Apache-2.0 licensed. The project labels itself: ai agent, ai coding agent, ai coding assistant, course, curated list and programming examples.

building-a-coding-agent-from-scratch-course runs. An Argusic agent installed it in 4.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Installed and built with uv, 2978 unit tests and 80 integration tests pass, format and lint clean, decode CLI reports version 0.1.0
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

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.02 (measured)
recorded runs: 2
last tested: 2026-09-19
stars: 465
forks: 126
open issues: 1
watchers: 9
size: 52 MB
created: 2026-06-19
last push: 2026-09-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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.

Install time: 5 minutes
Cold machine to finish: 5 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: uv run decode --version returned "decode, version 0.1.0"; make unit-tests: 2978 passed, 1 skipped; make integration-tests: 80 passed, 34 skipped; make format-check: 346 files already formatted; make lint-check: All checks passed
Model tokens used: 42,509
Exact commit tested: 798a1e7ad07c
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.

    'launch_succeeded': True,
    'install_minutes': 4.5,
    'errors': [],
    'test_depth': 'tier1_real',
    'verified_how': 'uv run decode --version returned \\\"decode, version 0.1.0\\\"; make unit-test…
    'final_state': 'Installed and built with uv, 2978 unit tests and 80 integration tests pass, for…
}))
\"" in /work/repo
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 4.5, "errors": [], "test_d…
tokens used
42,509

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 4.5 minutes, faster than the median of the 11 comparable projects Argusic has measured.
Nothing broke on the way: zero errors between clone and running.
Ran without a GPU, so it does not need one to start.
Licensed Apache-2.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

Of the 12 ai-agent projects Argusic has installed and timed, building-a-coding-agent-from-scratch-course was the 4th fastest to reach a running state, and 9 of 12 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 4.5 minutes after the clone.
Following its own README: the documented path worked with nothing to fix.

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	2/3	Runs	100.00	0.02	2026-09-19 16:21 UTC
Argusic Runner	1/3	Runs	100.00	0.03	2026-09-18 07:23 UTC

Topics (from GitHub)

ai-agent ai-coding-agent ai-coding-assistant course curated-list programming-examples

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/building-a-coding-agent-from-scratch-course.svg)](https://argusic.com/subject/building-a-coding-agent-from-scratch-course)

Questions

Does building-a-coding-agent-from-scratch-course run?: Yes. building-a-coding-agent-from-scratch-course runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test building-a-coding-agent-from-scratch-course?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 798a1e7ad07c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test building-a-coding-agent-from-scratch-course?: The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does building-a-coding-agent-from-scratch-course take to install?: 4.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 building-a-coding-agent-from-scratch-course need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing building-a-coding-agent-from-scratch-course?: Nothing did, in the recorded run: zero errors between clone and running.
How does building-a-coding-agent-from-scratch-course compare with the alternatives?: Of the 12 ai-agent projects Argusic has installed and timed, building-a-coding-agent-from-scratch-course was the 4th fastest to reach a running state, and 9 of 12 reached one at all.
Where is the evidence for building-a-coding-agent-from-scratch-course?: 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.