Latest stats on Claude Commits #039

AI Focus

Latest stats on Claude Commits

Following on from my post “Damn Claude, that’s a lot of commits”, I thought this follow up Tweet 6 months later would be a banger.

Turns out nope.

That being said, I thought I would run it again a month later and see what the current status is and document it here.

In the March post Claude Code had gone from 180K public GitHub commits a week to 2.6 million in six months, and I called the late-December 2025 curve an inflection. I re-ran the same scripts this weekend for the 52 weeks ending today, and the March number is now a quarter of the current weekly rate.

Claude Code weekly commits on GitHub, November 2025 to November 2026

Claude Code weekly commits on public GitHub, 52 weeks to 1 November 2026

When I looked at it in March I was quite surprised by how steep the growth was, however the shape has changed since then. The first half of the year was a steady climb: 243K, 500K in the new year, 1 million by February, 2.5 million by the end of March. After this latest run you can see that it sat between 2.4 and 4.2 million a week from April through August. Then the second pop starts in the week of 31 August 2026 and does not stop: 5.0M, 4.7M, 5.4M, 6.3M, 8.0M, 8.7M, 8.6M, 10.1M, 10.3M. Something changed at the end of August and while the commit data doesn’t say it around the same time Fable 5.1 launched and then Opus 5.5 launched later in the month, but I don’t actually know what really changed. What it does show is Claude Code’s weekly output almost doubling in two months, after five months of steady growth.

What I find incredible in the moth since I run the data for my Tweet we have gone from 7M to over 10 million commits a week.

The methodology here is to use the GitHub Search API and sample the number of results that are returned (it’s not consistent so you have to sample it a couple of times).

If you are interested in how this compares to other tools? Then you can see below:

AI coding agent commits per week, all tools, with a detail panel excluding Claude

AI coding agent commits per week. Top: everything on one scale. Bottom: everyone except Claude.

While it looks like Claude is now 14x the next tool over the year, and 36x it in the latest week, you have to remember that not every other tool consistently openly attributes commits to the tool the user used, also, here are more caveats:

  • Public repositories only. Everything enterprise is invisible to this.
  • Detection is uneven. Claude Code writes a trailer on every commit by default, so it is over-counted relative to tools that leave no trailer, or that changed how they mark commits during the year.
  • GitHub’s commit search is noisy, and noisier than it was. In September, running the same weekly query twice gave the same answer to within a commit. This weekend the same query for the week of 24 August returned 2.5M, 3.4M, 4.2M and 4.7M on four consecutive tries. I sampled every Claude week at least twice and took the median, and the other tools once, so treat individual weeks as ±20% and the trend as the thing that’s solid. The final week was pulled on a Sunday afternoon, so it is a day short (note to self: fix this - I normally write on Sundays :)
  • Github Search can also not be consistent if someone makes a private repository public or private then this can impact historic stats from previous runs.

The raw data is downloadable: commits, 52 weeks to 2026-11-01. Every row includes the GitHub search URL used to generate it and the individual samples, so you can check any number yourself. The scripts are the same ones linked from the March post.

These numbers now live on a page that is re-measured at the start of every month, with every figure from this post and the March one shown next to its current value: aifoc.us/stats as well as other data that I’ve used in other posts (such as Dead Framework Theory) that I care about.

Add a note

Notes are reviewed before other readers see them.

Subscribe to the Newsletter

Get the latest essays and projects on how AI is changing the medium of the web delivered straight to your inbox.

wat the heck: why ship javascript when nobody reads the code? - 2026-10-30

setting goals - 2026-10-25

how might a modern lighthouse work with large language models? - 2026-07-03

does a url in a prompt steer an llm's output toward its content? - 2026-07-03

please mind the model gap - 2026-06-07

I think i've got it: WebMCP is the new web intents - 2026-06-06

building a claw in the browser - 2026-05-22

shipping a prompt - 2026-05-22

how fast do ai models go stale? - 2026-05-18

are pwas cooked? - 2026-05-17

a business in a box - 2026-05-10

How might a browser be developed? - 2026-05-03

agent-do: my agent loop - 2026-05-01

webmcp is the new web intents ... maybe - 2026-04-27

damn claude, that's a lot of commits - 2026-03-30

the token salary - 2026-03-27

the llm whisperer - 2026-03-08

the prompt is the program - 2026-02-21

If NotebookLM was a web browser - 2026-01-25

the browser is the sandbox - 2026-01-25

the projects behind my ai focus posts - 2026-01-02

hyper content negotiation - 2025-11-27

headless cms was a stopgap - 2025-11-23

dead framework theory - 2025-10-12

intercepting the web with an llm - 2025-09-21

calling apis from the browser shouldn't mean exposing keys - 2025-08-22

hypermedia was always the point - 2025-08-18

web components are packaging for ai-generated ui - 2025-07-16

what happens to the cms when ai can build the site? - 2025-07-05

what token slinging taught me about ai costs - 2025-06-30

on-device ai needs a trust model - 2025-06-12

AI Assisted Web Development - 2025-06-04

embedding is the web's composability superpower - 2025-05-28

ai agents make mashups worth revisiting - 2025-05-24

what falling ai model latency means for the web - 2025-05-22

A link is all you need - 2025-05-17

llms are becoming the new super-apps - 2025-05-12

this transition feels different - 2025-05-09