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.

This is a workshop designed for Amazon Bedrock a foundational model service.

aws-samples/amazon-bedrock-workshop ↗

aws-samples/amazon-bedrock-workshop AI coding statistics: 25.2%

of 127 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
25.2% agent · top contributor 81.3%2 contributors
individual

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

32
agent commits
95
other considered commits
2
agent contributors
81.3%
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

32assisted
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-030%3
2026-0437.2%86
2026-050%4
2026-060%32
2026-090%2

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic3225.2%

Inspect the matches

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

Matched commit samples

  • 8b378f27 on GitHubAdd learning paths section header and active path indicatorClaude Code
  • 6abff742 on GitHubAdd interactive MCQ with clickable buttons and answer validationClaude Code
  • 2103524d on GitHubDetect and intervene when user blindly clicks Run/Next repeatedlyClaude Code

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 window159
Merge commits removed−20
CI / dependency bots removed−12
Considered127

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 aws-samples/amazon-bedrock-workshop

Scan another repository