← the index
daytonaio/daytona
0.3%
of 736 commits were committed by an AI agent — a floor, not an estimate
0.3% agent · top contributor 50%2 contributors
individual

One person is driving this. The headline number reflects a single contributor's workflow, not a project-wide shift.

2
agent commits
734
human commits
2
agent contributors
50%
largest contributor

Assisted or autonomous

2assisted
0autonomous

Assisted — a developer’s identity authored the commit and the agent added itself as co-author. The agent ran git commit during a working session, with a person there. Autonomous — a bot identity is the author, no human in the loop. Across the whole index, 93.7% of agent commits are assisted.

Agent share by month

Feb26
Mar26
Apr26
May26
Jun26

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

Which agents

Cursor AgentAnysphere10.1%
Claude CodeAnthropic10.1%

Verify it yourself

Sample commits that matched. Every one links to GitHub — check the trailers.

  • 0a3dfd9ffix(opencode): make git sync work on slim sandboxes (#4952)Cursor Agent
  • 36025e46fix(api): jest support for uuid v14 ESM-only packageClaude Code

What was excluded

Commits in window925
Merge commits removed0
CI / dependency bots removed189
Considered736

Bots are excluded from the denominator entirely. Counting dependabot as “AI-written code” is the fastest way to produce a meaningless number.

How this was measured

Measured over February–August 2026, cloned directly. Detection is deterministic string matching against signatures agents write about themselves — no heuristics, no style analysis. Merge commits and CI bots are excluded from the denominator. The figure is a floor: squash merges strip trailers, so real usage is higher. Contributor counts are aggregate — no individual is named.

Run it yourself: npx qmmit-cli daytonaio/daytona

Scan another repository