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

rtk-ai/rtk ↗

rtk-ai/rtk AI coding statistics: 31.9%

of 1,361 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
31.9% agent · top contributor 40.1%50 contributors
org-wide

Adoption is broad. Many contributors are committing agent-authored work, which is what a real organisational rollout looks like.

434
agent commits
927
other considered commits
50
agent contributors
40.1%
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

434assisted
0autonomous

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-0278.9%109
2026-0324.9%221
2026-0417.4%190
2026-0511.1%135
2026-0612.1%116
2026-078.3%157
2026-0828.8%163
2026-0963.3%270

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic43331.8%
Cursor AgentAnysphere10.1%

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 window1,944
Merge commits removed−506
CI / dependency bots removed−77
Considered1,361

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
rtk-ai/rtk
Default branch
develop
Resolved HEAD
5e0f92cd108fc5a985022c5eb525a401f97fa11f ↗
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.

CohortRust · 117 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 33 of 150 ecosystem repositories excluded
Agent-commit share position94th percentile

Midrank percentile; equal shares split the tied positions.

Repository
31.9%
Cohort median
2%
Share rank
8 / 117
0th50th100th

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

Continue exploring

Claude Code commitsBrowse repositories with detected Claude Code signatures →Cursor Agent commitsBrowse repositories with detected Cursor Agent 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 rtk-ai/rtk

Scan another repository

Try