AIToday
Large Language ModelsAI Coding AssistantsTHE DECODERPublished: Aug 14, 2026, 22:00 JST2 min read

Claude Code merges 46% of maintenance pull requests in Anthropic test

Claude Code merges 46% of maintenance pull requests in Anthropic test

3 Key Points

  1. What happened

    Anthropic tested Claude Code handling daily software maintenance on its own in-house apps for the past few weeks. Claude created 388 pull requests across Anthropic's repositories; 180 were merged after human and automated review, a merge rate of about 46 percent.

  2. Why it matters

    The test shows that AI can reduce the burden of repetitive maintenance work on human developers. Claude runs 12 specialized routines—covering crash fixing, dead-code removal, duplicate merging, test cleanup, and logic simplification—using plain-language Slack prompts with no elaborate prompt engineering required.

  3. What to watch

    More than half the auto-generated pull requests did not merge, signaling both limits and potential of the approach. Anthropic engineer Boris Cherny describes the results as "surprisingly positive" and "early signs of life" for autonomous AI-powered maintenance, and the company is exploring ways to speed up the merge process for mechanical changes.

Ask the AI about this article →

Context & Analysis

Anthropic's experiment with Claude Code represents a pragmatic exploration of how AI can absorb repetitive software maintenance tasks. Rather than a theoretical test, the company deployed Claude against its own codebase, running 12 distinct maintenance routines—from crash fuzzing to duplicate-code merging to flaky-test fixing—each with a specific role in the broader maintenance pipeline. The setup is deliberately unglamorous: plain-language Slack prompts, no complex prompt engineering, and straightforward human review gates. This approach avoids over-engineering the system while keeping humans in control of what ships.

The 46 percent merge rate after review is telling. It indicates that Claude can produce valid, useful pull requests at scale—enough to meaningfully reduce developer toil—but also that nearly half the proposals need refinement or rejection. The team's iterative approach (tweaking routines when they fail) suggests a path toward improvement over time. Cherny's framing as "early signs of life" rather than "solved" is honest and important: the experiment shows potential but does not yet prove that fully autonomous maintenance is ready for production. The fact that Anthropic is already looking at ways to accelerate the merge pipeline suggests confidence in the direction.

FAQ

What platforms does Claude Code maintain?
Claude Code runs daily maintenance routines across iOS, Android, desktop, web, CLI, and the Agent SDK, coordinated through a dedicated Slack channel called "proj-claude-maintains-apps."
How does Claude Code receive its maintenance tasks?
Boris Cherny, the Anthropic engineer who created Claude Code, delegates tasks using plain-language Slack messages with no elaborate prompt engineering—for example, telling Claude to perform crash fuzzing on specific platforms using real apps and create pull requests with fixes.
What happens when Claude Code's pull requests are rejected?
When a pull request does not merge, the team tweaks the routine so Claude performs better the next day; this tuning sometimes takes a few days.

Get the latest Large Language Models news every morning

For example, today's edition would include:

  • Nvidia revives Rubin CPX chip with major redesignYahoo Finance AI · 2h ago
  • AI advice followed by 79%, but well-being unchangedITmedia AI+ · 5h ago
  • Enterprises face agent governance gapSiliconANGLE AI · 8h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleServiceNow CFO: Three questions every AI investment must answer