Staged rollout of shipped code: 7 sourced coding agent stories
The shipped code goes out gradually: feature flag, canary with rollback, pre-release, closed testing or a rehearsed data migration. This technique sits in the Release stage. Of the 7 stories, 2 were published by a tool vendor and 5 by the people who did the work. 5 involve an existing codebase and 2 started from scratch. Every number links to where it was published.
An autonomous Claude Code agent ships 340+ production deploys behind a three-stage gate it cannot edit
Yureki Lab (dev.to author) · Claude Code
CaveatsSelf-reported by a single pseudonymous author on dev.to about one team and one system. The company, codebase size and traffic are not named, and none of the numbers are independently checked. The author says every incident the gate caught was a wrong answer ("None of them produced a single 5xx"); commenters point out a 5% canary over 10 minutes may miss low-volume regressions, and that the canary thresholds come from the deploy block the agent writes, so the agent still chooses how strict its own check is. No figures are given for the agent itself (token cost, time per task) or for how long the gate took to build.
"340+ production deploys with zero human-paged incidents" over six months
Deploys since the gate
GitHub ports the Copilot agent runtime from TypeScript to 800K+ lines of Rust, mostly by one engineer
GitHub (Microsoft) · GitHub Copilot
CaveatsPublished by GitHub about its own product. The author notes team members also contributed (bindings, packaging, reviews), and that performance numbers include other changes from the same period.
832,378 lines
Production Rust written
Engineer ships 11 Flutter apps and games to both app stores in two months with Claude Code and Codex, on $40 a month
Seif Ibrahim · Claude Code, OpenAI Codex
CaveatsSelf-reported. The apps are small, offline games and utilities. No line counts or revenue figures.
11 on iOS and Android
Apps shipped
Claude plans and reviews, Codex builds: a production music site migrated from a React SPA to Next.js in 36 hours
Nik McFly · Claude, OpenAI Codex
CaveatsSelf-reported by the site owner on his own blog. A single, fairly small site. The post does not say which Claude product (Claude Code or chat) was used. A staging Docker build filled the server disk and briefly caused production API errors during the migration. The author notes the performance numbers are for this migration only.
36 hours
Migration time
Datadog migrates its live Stream Router from FoundationDB to PostgreSQL with Claude and Cursor; 45-minute operations now take ~1 second
Datadog · Claude, Cursor
CaveatsSelf-reported by the Datadog team that did the work. The AI tools were not autonomous: humans designed the schema, reviewed every generated skeleton, and wrote the optimised SQL (batching, UNNEST, CTEs), which the models then copied. Most of the performance and cost gains come from the new relational design, not from the AI tools; the post credits AI with making the implementation possible in the time frame. No count of methods, PRs or lines is given, and token spend is described only as significant.
~3 months (Dec 2025 – Feb 2026); proof of concept in 4 weeks
Design to production
Eventship replaces a quoted 6-month, 5-person rebuild with 5 weeks of solo Claude Code work and migrates 20,000 users
Eventship · Claude Code
CaveatsSelf-reported by the founder. A friend wrote the data migration script. Launch had an outage from unconfigured GCP scaling, plus edge-case bugs afterwards. No line counts or test numbers given.
5 weeks, solo
Time
Wiz ports a 50,000-line Python PDF library to Go in about 20 hours with Claude Code
Wiz · Claude Code
CaveatsPublished by Anthropic as a customer story. The 2–3 month estimate and the '20-30x estimated output multiplication' are the company's own estimates. The page shows no publish date.
~50,000 lines of Python (pypdf)
Source size