llmcoderlab

Experiments in AI‑assisted software engineering.

LLM Coder Lab puts large language models to work on real software — then publishes what happened. Benchmarks on genuine tasks, complete build logs, and field notes on what these tools can actually do, where they break, and how to get the most out of them.

4
models tested
9
challenges
64
attempts graded
18
failures caught
145k
tokens out
3
findings published

From the bench log

07-17 21:42qwen3-30b-a3b · word-ladder · agenticerror
07-17 21:27qwen3-30b-a3b · word-ladder · oneshot100
07-17 21:21qwen3-30b-a3b · vowel-count · agentic100
07-17 21:19qwen3-30b-a3b · vowel-count · oneshot100
07-17 21:18qwen3-30b-a3b · text-stats · agenticerror
07-17 21:03qwen3-30b-a3b · text-stats · oneshoterror
all runs →
01

Benchmarks

Head-to-head coding evaluations on real tasks — not toy puzzles. Frontier and open-weight models, scored on working software.

02

Build logs

Complete, unedited session transcripts of real projects built with LLM agents — every prompt, every wrong turn, every fix.

03

Field notes

Practical techniques from the bench: agent workflows, prompting patterns, and the failure modes nobody writes up.

One-shot

1 model call
  • One prompt, one reply — complete files, blind
  • No tools, no test access, no feedback, no retries
  • Measures raw code generation
VS

The harness

≤24 turns
  • Isolated workspace, five tools: read, write, list, run_tests, done
  • Sees real pytest failures, repairs, iterates
  • "Done" only counts if the suite is green
  • Measures the engineering loop — including knowing when to stop

Every model runs every challenge both ways — the delta is the finding. Run 1: the same model solved fizzbuzz in 6 seconds and one call one-shot, then took 90 seconds and 24 calls to the same score in the harness — because it never realized it was finished. Read the field notes or inspect the harness, prompts and source included.

First results are in. See the leaderboard — more models and harder challenges are coming.