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

google-gemini/gemini-cli ↗

google-gemini/gemini-cli AI coding statistics: 9%

of 2,061 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
9% agent · top contributor 46.5%51 contributors
org-wide

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

185
agent commits
1,876
other considered commits
51
agent contributors
46.5%
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

182assisted
3autonomous

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-026.5%586
2026-039.1%680
2026-048.2%380
2026-059.9%232
2026-0614.3%49
2026-0718.8%48
2026-0813.3%60
2026-0926.9%26

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

Which agents

AgentVendorCommitsShare
Gemini CLIGoogle1859%

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 window2,062
Merge commits removed−0
CI / dependency bots removed−1
Considered2,061

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
google-gemini/gemini-cli
Default branch
main
Resolved HEAD
6a466a7e2fe2b1255752c1e74f69b31f0216084d ↗
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.

CohortJS/TS · 376 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 194 of 570 ecosystem repositories excluded
Agent-commit share position63rd percentile

Midrank percentile; equal shares split the tied positions.

Repository
9%
Cohort median
5.4%
Share rank
141 / 376
0th50th100th

Percentile = (repositories below + half of 2 tied repositories) ÷ 376.

Continue exploring

Gemini CLI commitsBrowse repositories with detected Gemini CLI 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 google-gemini/gemini-cli

Scan another repository

Try