AI & Language Benchmarks

The 600-Run Verdict: What Happens When an AI Agent Writes Your Pipeline in 13 Languages

A Ruby core committer ran Claude Code 600 times across 13 languages to build a tiny Git clone. The results reshuffle the Ruby-vs-Python argument — and land right as GitHub ships a desktop app for orchestrating fleets of coding agents.

07 · 27 · 2026 · Interactive briefing · ~6 min

Watch the benchmark harness run

This is a scripted replay of the actual test loop researcher Yusuke Endoh used: Claude Code (Opus 4.6) implements init, add, commit, and log for a mini Git clone, 20 times per language, timed and priced per run. Hit play, or jump straight to the finish.

agent-bench.sh — claude-code

Benchmark explorer — all 15 language configs

Real results from 600 runs (40 per config, v1+v2 tasks). Click a header to sort, click a chip to filter by family, click a row for the story behind the number.

All 15 Dynamic + Type Checker Static Functional
Language Avg. Cost Time (v1+v2) LOC (v2) Pass Rate

Source: Yusuke Endoh’s ai-coding-lang-bench (GitHub), reported by InfoQ, April 2026. ± values are standard deviation across 20 runs per phase.

Ruby or Python? Weight what matters to your team

The benchmark says Ruby edges Python by a hair on agent-authored code. But your team isn’t an agent. Pick the priorities that matter for your actual project and see how the case shifts.

🤖Agent run costCheapest per AI task
Agent speedFastest wall-clock
🛡️Type safetyStatic guarantees matter
📦Data / ML ecosystemLibraries, notebooks, ML
🛠️Web app velocityConvention-heavy frameworks
👥Hiring pool sizeMarket availability
Select 1–3 priorities above
Ruby ≈ Python
RUBY
50%
PYTHON
50%
Both passed 40/40 benchmark runs. Ruby was $0.02 cheaper and 1.5s faster per run on average — pick based on your own priorities, not just the agent’s.

Your CI pipeline is about to have opinions on your language

GitHub’s new Copilot desktop app (public preview, rolling out through summer 2026) lets teams run multiple coding agents at once against real repos — triaging issues, opening PRs, and looping on review feedback largely unattended. GitHub also shifted Copilot billing to usage-based, per-token pricing this year. Put those two facts together and the benchmark above stops being trivia: if your agents are writing glue scripts, Rakefiles, CI steps, or Lambda handlers, the language they write in changes your bill — not by a rounding error, but by up to 2.3× (Ruby/Steep’s $0.84 vs. plain Ruby’s $0.36).

Practical takeaway: for AI-agent-authored automation code specifically — the boring scripts nobody hand-reviews line by line — dynamic languages without a strict type checker bolted on came out cheapest and fastest across the board. Save the static typing for the code your humans own.

ci-agent-step.yml — sample GitHub Actions wiring
# Route agent-authored automation to a cheap, fast language runner,
# reserve statically-typed jobs for human-owned services.
name: agent-automation
on: [issue_comment]
jobs:
  run-agent-task:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: "Let Copilot / Claude Code write + run the fix"
        run: |
          # Ruby & Python both hit 40/40 pass rate in the 2026 benchmark;
          # Ruby ran ~2% cheaper, Python's ecosystem is broader.
          bundle exec rake agent:apply_patch
          bundle exec rspec --fail-fast