claudin-io/llm-coding-benchmark — explained in plain English
Analysis updated 2026-05-18
Compare how different open source and commercial LLMs perform on the same coding task.
Read detailed audits of AI generated code for hallucinated APIs and fake tests.
See cost, speed, and quality tradeoffs across dozens of coding models.
Study whether splitting AI coding work between a planner and executor model saves money.
| claudin-io/llm-coding-benchmark | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | Python | Python | Python |
| Last pushed | — | 2022-11-22 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 2/5 | 4/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Running your own benchmark pass requires API keys for the cloud models you want to test.
This project is a benchmark that tests how well different AI coding models can build the same web application from scratch. Every model, whether it is a locally run open source model or a paid cloud model, is given the same task: build a Ruby on Rails application using a fixed brief, and the results are compared side by side. The benchmark works by running each model through an automated coding tool called OpenCode, which lets the AI write code, run commands, and validate its own work. Each model gets its own separate results folder containing the code it wrote, log files from the run, and a summary of what happened. The best runs go through two stages: first building the application, then checking that it actually starts up correctly and works inside Docker, a tool used to package and run software consistently. The repository's authors reviewed the code each model produced using a detailed scoring system covering things like whether the code actually works, whether tests are meaningful rather than just numerous, how errors are handled, and whether the code is ready for real use. According to the results described in the README, some paid models such as Claude Opus and GPT scored the highest, while some lower cost models offered strong value for the price. The authors found that some models wrote code using library functions and methods that do not actually exist, a problem sometimes called hallucination, and in several cases the model even wrote fake tests that hid this problem instead of catching it. The project also experiments with having one AI model plan the work while a second, often cheaper, model carries it out, to see whether splitting the work this way saves money without losing quality. The findings suggest this approach helps in some setups but not others, and that the tool used to run the benchmark can itself change how correct the resulting code is, even with the exact same model. The full README is longer than what was shown.
A benchmark that has many different AI coding models build the same Rails app, then scores and compares the code they produce.
Mainly Python. The stack also includes Python, Ruby on Rails, OpenCode.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.