Pulse
2026-09-18-v3.0
Dataset
2026-10-27-catalog-ai-v2
Ruleset
b2e8889c66f7
Scanned
2026-10-27
Window
February–September 15, 2026
Catalog tracking observation. This repository is measured with the same fixed window and ruleset, but it is not part of the published benchmark or its aggregate claims.

Experience TizenTube on other devices that are not Tizen.

reisxd/TizenTubeCobalt ↗

reisxd/TizenTubeCobalt AI coding statistics: 0.4%

of 1,720 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
0.4% agent · top contributor 57.1%4 contributors
team

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

7
agent commits
1,713
other considered commits
4
agent contributors
57.1%
largest contributor

What shapes this result

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

Assisted or autonomous

7assisted
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.

Agent share by month

Agent-attributed commit share by month
MonthAgent shareConsidered commits
2026-021.9%162
2026-033.2%124
2026-040%268
2026-050%225
2026-060%289
2026-070%191
2026-080%292
2026-090%169

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

Which agents

AgentVendorCommitsShare
Gemini CLIGoogle70.4%

Inspect the matches

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

Matched commit samples

  • f4a05f90 on GitHubCherry pick PR #9523: Cherry pick PR #9150: Refactor Cobalt application liGemini CLI
  • b402b4b5 on GitHubCherry pick PR #9232: Cherry pick PR #8928: Implement basic application prGemini CLI
  • 4880484b on GitHubCherry pick PR #7784: Revive h5vcc_settings for in-memory experimentation Gemini CLI

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,745
Merge commits removed−23
CI / dependency bots removed−2
Considered1,720

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

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 reisxd/TizenTubeCobalt

Scan another repository