llms.blog
AI

Anthropic lets Claude Code run daily maintenance on its own apps

Anthropic is running an experiment in which Claude Code performs daily maintenance on the company's own software, and the results are already measurable. Across the first few weeks, the system opened 388 pull requests and had 180 merged after review, a roughly 46 percent acceptance rate. Boris Cherny, the Anthropic engineer who created Claude Code, described the setup in a LinkedIn post. Through Anthropic's internal Tag integration, Claude runs a set of scheduled routines every day inside a de

axc
axc
2 min
Anthropic lets Claude Code run daily maintenance on its own apps

Anthropic is running an experiment in which Claude Code performs daily maintenance on the company's own software, and the results are already measurable. Across the first few weeks, the system opened 388 pull requests and had 180 merged after review, a roughly 46 percent acceptance rate.

Boris Cherny, the Anthropic engineer who created Claude Code, described the setup in a LinkedIn post. Through Anthropic's internal Tag integration, Claude runs a set of scheduled routines every day inside a dedicated Slack channel called "proj-claude-maintains-apps," spanning the company's iOS, Android, desktop, web, CLI, and Agent SDK codebases.

Claude Code maintenance routines

The work is mechanical upkeep, not new feature development. Cherny listed twelve recurring routines. A "Crash Fuzzer" launches the apps in a simulator, taps around to trigger crashes, finds the root cause, and opens a fix. A "Dead-Code Remover" strips out code that static analysis shows is unreachable, first adding logging to confirm the code really is unused before deleting it. Other routines simplify business logic, merge duplicate implementations, prune tests that can never fail, remove stale feature flags, and fix flaky continuous-integration tests.

The instruction style is deliberately plain. Cherny said he simply told Claude in natural language to start daily crash-fuzzing routines on iOS, Android, and desktop using the real apps without mocks, trigger crashes, and open pull requests with fixes.

Quality control sits between the AI and the main branch. Each pull request passes through automated Claude Code review and then human review. Cherny said Claude usually gets the change right on the first try, and when it does not, the team adjusts the routine so the system performs better the next day. That tuning can take a few days. Anthropic is now looking at ways to speed up merging for this kind of mechanical change.

The 46 percent merge rate is a double-edged signal. More than half of the auto-generated pull requests did not make it through review, underscoring the limits of fully autonomous maintenance. But 180 accepted changes in a few weeks show the approach can absorb a meaningful slice of repetitive engineering work that would otherwise occupy human developers.

Sources

AIClaude CodeAnthropicSoftware EngineeringCoding Agents
ShareX (Twitter)LinkedIn

Written by

axc

More to read

  • Stealth Model 'Ox Alpha' Surfaces with 1M Multimodal Context and 100 Trillion Daily Token Allocation

    An anonymous frontier model named "Ox Alpha" has launched across OpenRouter and the OpenCode developer environment, offering free access backed by a reported 100 trillion tokens per day in serving capacity. The model features a 1,048,576-token context window with native multimodal support spanning text, image, and video inputs. The unannounced release follows a pattern of stealth evaluations across AI model aggregators, where frontier labs deploy pre-release checkpoints to collect blind compara

    1 min

  • OpenAI Cuts GPT-5.6 Sol API and Coding Tool Pricing by Over 20%

    OpenAI has lowered developer pricing for its flagship GPT-5.6 Sol model across its API and developer toolchain for a three-month promotional window. The rate adjustment reduces input token costs by 20% and output token costs by 33.3%, bringing standard short-context inference to $4.00 per million input tokens and $20.00 per million output tokens. The revision comes amid intensified developer pricing pressure across the frontier model ecosystem, particularly following aggressive pricing from com

    1 min

  • Hierarchical Tree Retrieval in Production RAG: Architecture, Recursive Clustering, and Serving Economics for RAPTOR

    Production Retrieval-Augmented Generation (RAG) pipelines routinely hit a fundamental structural ceiling: flat chunk retrieval. Standard retrieval architectures segment ingested documents into uniform, contiguous chunks (typically 100 to 512 tokens), embed them in a vector space, and fetch top-k nearest neighbors based on cosine similarity. This design functions well for granular, needle-in-a-haystack fact lookups ("What was the Q3 gross margin for EMEA?"). However, it fails on thematic, holist

    1 min