Pulse
2026-09-18-v3.0
Dataset
2026-09-18-v3.0
Ruleset
b2e8889c66f7
Scanned
2026-09-16
Window
February–September 15, 2026
Local to this browser

01Result

omacom/omarchy ↗

omacom/omarchy AI coding statistics: 19.6%

of 2,992 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
19.6% agent · top contributor 74.9%75 contributors
team

A small group is using agents. Adoption has spread beyond one person but is not project-wide.

586
agent commits
2,406
other considered commits
75
agent contributors
74.9%
largest contributor

02Drivers

What shapes this result

Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.

Assisted or autonomous

584assisted
2autonomous

Assisted — a developer’s identity authored the commit and the agent added itself as co-author. Autonomous — a bot identity authored the commit without a human identity attached. Across the whole index, 96% of agent commits are assisted.

Agent share by month

Agent-attributed commit share by month
MonthAgent shareConsidered commits
2026-020.8%355
2026-033.3%152
2026-043.9%229
2026-050.7%976
2026-060.8%263
2026-0756%439
2026-0856.8%484
2026-0941.5%94

Peak month: 56.8%. Bars are scaled to that peak, not to 100%.

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic54618.2%
OpenAI CodexOpenAI581.9%
GitHub CopilotGitHub160.5%

03Evidence

Inspect the matches

Public commit samples let you inspect the signatures behind the aggregate result.

Matched commit samples

04Method

What entered the denominator

The result begins with commit history, removes merges and routine automation, and reports literal agent signatures as a lower bound.

Exclusion ledger

Commits in window3,327
Merge commits removed−335
CI / dependency bots removed−0
Considered2,992

Bots are excluded from the denominator entirely. Agent attribution requires a literal supported signature; no code-style inference is used.

05Provenance

Pinned to a source state

This observation names the repository state, release, and detector that produced it. Use these identifiers when reproducing or citing the result.

Dataset release
2026-09-18-v3.0
Scan date
2026-09-16
Ruleset
sha256:b2e8889c66f72c18a61839f0bf1a9f77b5481ba2def044dba33c797b2f2bdcae
Canonical repository
omacom/omarchy
Default branch
quattro
Resolved HEAD
2fbac0c8e88eca704af1650ce721a494bd11a3d0 ↗
Resolved
2026-09-16
Measurement window
February–September 15, 2026
Download observation JSONDeterministic export · same values as this page

06Peer context

Position among comparable repositories

The cohort uses the same release and measurement window, then narrows to the repository’s ecosystem and removes low-activity observations.

CohortShell · 23 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 21 of 44 ecosystem repositories excluded
Agent-commit share position80th percentile

Midrank percentile; equal shares split the tied positions.

Repository
19.6%
Cohort median
1.5%
Share rank
5 / 23
0th50th100th

Percentile = (repositories below + half of 1 tied repository) ÷ 23.

Continue exploring

Claude Code commitsBrowse repositories with detected Claude Code signatures →GitHub Copilot commitsBrowse repositories with detected GitHub Copilot signatures →OpenAI Codex commitsBrowse repositories with detected OpenAI Codex signatures →GitHub AI commit analyzerInspect another repository with the same evidence model →
Reproduce this observation

Run the same detector locally.

Deterministic signature matching; no code-style inference. Squash merges can remove trailers, so this result remains a measured floor.

npx qmmit-cli omacom/omarchy

Scan another repository

Try