Claude Code now runs daily maintenance on Anthropic's software with a 46 percent merge rate
Anthropic is testing Claude Code for autonomous daily maintenance of its own software, with Boris Cherny overseeing the experiment Over a few weeks, Claude generated 388 pull requests across iOS, Android, desktop, web, CLI, and Agent SDK platforms, achieving a 46% merge rate after human review Twelve specialized maintenance routines were deployed, including Crash Fuzzer, Dup Unifier, Dead Code Removal, Flaky-Test Fixer, and Logic Bug Fixer The system operates through a dedicated Slack channel us
Analysis
TL;DR
- Anthropic is testing Claude Code for autonomous daily maintenance of its own software, with Boris Cherny overseeing the experiment
- Over a few weeks, Claude generated 388 pull requests across iOS, Android, desktop, web, CLI, and Agent SDK platforms, achieving a 46% merge rate after human review
- Twelve specialized maintenance routines were deployed, including Crash Fuzzer, Dup Unifier, Dead Code Removal, Flaky-Test Fixer, and Logic Bug Fixer
- The system operates through a dedicated Slack channel using plain-language prompts without elaborate prompt engineering
- Cherny describes results as "early signs of life" for autonomous AI-powered app maintenance, with ongoing efforts to improve merge rates
Why It Matters
This experiment represents one of the most concrete real-world demonstrations of AI agents handling sustained, autonomous software maintenance at scale within a major tech company. For AI practitioners and engineering leaders, it provides empirical data on what current LLM-based coding agents can and cannot handle in production environments, offering a realistic benchmark for autonomous developer tooling.
Technical Details
- Architecture: Claude Code operates via Tag integration, running daily routines through a dedicated Slack channel ("proj-claude-maintains-apps") across all Anthropic platforms
- Twelve specialized routines: Crash Fuzzer (simulator-based crash detection and fix generation), Dup Unifier (merges similar abstractions), Dead Code Removal (with logging verification), Logic Simplifier, Logic Bug Fixer, Useless Test Pruner, Flaky-Test Fixer, Abstraction Improver, Abstraction Police, Ant-only Shipper, and Shipped-Feature Inliner
- Prompting approach: No elaborate prompt engineering; Cherny uses plain-language Slack messages instructing Claude to run routines on real apps without mocks
- Performance metrics: 388 PRs generated, 180 merged (46% rate); Claude typically gets PRs right on first attempt, with iterative tuning taking a few days when adjustments are needed
- Review pipeline: Combination of automated Claude Code review and human review before merging
Industry Insight
- The 46% merge rate suggests autonomous AI maintenance is viable for mechanical, well-scoped tasks but still requires significant human oversight for complex or high-risk changes; companies should start with narrow, low-stakes maintenance routines before expanding scope
- The plain-language prompting approach demonstrates that sophisticated prompt engineering may be less critical than previously assumed for agent-based development workflows, potentially lowering the barrier to adoption
- The iterative tuning model—where routines are refined over days based on failures—indicates that organizations should expect a learning curve and build feedback loops into their AI agent deployment strategies rather than expecting plug-and-play reliability
Disclaimer: The above content is generated by AI and is for reference only.