Coding agent unstated: 30 sourced stories
Stories whose source doesn't name the coding agent used. Several are studies that cover many tools at once. Of the 30 stories, 3 were published by a tool vendor, 22 by the people who did the work and 5 by independent researchers or press. 24 involve an existing codebase and 1 started from scratch. Every number links to where it was published.
Fergus ships 6.3× more weekly merges with the same-sized team, cutting PR merge time from 18 hours to 1.6
Fergus · Tool unstated
CaveatsSelf-reported by Fergus's engineering lead. The post does not name which coding agents or AI review tools they used. Throughput (up 500%) and weekly merges (6.3×) are related but separately stated; raw PR counts are not given. 6.3× overall vs 4.7× per author is explained as more merged PRs coming from outside the engineering team. They report a handful of outages even as change failure rate halved. Comparison window for the 6.3× figure is not dated beyond the same team size as 18 months ago.
6.3×, same sized Fergus Engineering team
Weekly code merges
Operum: two founders running six-role AI agent teams merge 296 PRs in 12 days, each gated on an AI tester approving the exact commit
Operum · Operum
CaveatsWritten by a co-founder about building Operum with Operum, in a post leading into its Product Hunt launch, so it promotes the product. The PR categories come from titles, not a diff audit, and the author says the PRs are small and PR count is the wrong scoreboard. Cursor is named as the app's default engine and recommendation; the post does not say which engine the team used for these 296 PRs, so the tool is Unstated. Revert and rework rates are not reported.
296 in 12 days (15–26 Oct 2026)
Merged PRs
Dropbox engineers use coding agents to ship 22 accessibility features and clear a test cleanup deferred for two quarters in one week for the new Dropbox launch
Dropbox · Tool unstated
CaveatsWritten by Dropbox engineers about their own launch. The post does not name the coding agents or models, and gives no counts of PRs, lines or time saved beyond the cleanup week. Some work described (tracing dependencies, writing adapters) is AI-assisted rather than delegated to agents.
Dropbox Tech blog (Pravi Garg, Sourabh Yerfule, Gennadiy Civil)
22 across Home, All Files, file previews and Photos
Accessibility features
Bloomberg's Automated Uplift ran LLM-assisted migrations across thousands of repositories: 2,333 PRs and 729 successful migrations
Bloomberg · Tool unstated
CaveatsWritten mostly by Bloomberg engineers who ran the work, with an academic co-author. Drafted from the abstract only; the abstract names no model or coding tool and gives no time or cost figures. 729 successes out of 2,333 PRs means many PRs did not result in a migration.
2,333 generated across two campaigns
Pull requests
Microsoft's Copilot Cowork team goes empty-repo to worldwide GA in 4.5 months with agents writing most of the code, then ports the live runtime from Python to Rust
Microsoft (Copilot Cowork) · Tool unstated
CaveatsSelf-reported Microsoft eng post. The specific coding-agent product is not named (only “agents”). Latency gain partly attributed to moving the agent loop out of the container, not Rust alone. No cost-per-turn claim.
13 Jan to 16 Jun 2026 (~4.5 months)
Empty repo to worldwide GA
Harvard study of 655 firms: AI agents raise code volume far more than shipped work, review becomes the bottleneck
655 firms (Jellyfish data) · Tool unstated
CaveatsCurrent version dated 1 Nov 2026 (first version 7 Jan 2026). The earlier version we first used covered 718 firms and ~300M events. Data from Jellyfish, an engineering analytics vendor; the authors state the conclusions are their own and that Jellyfish reviewed the paper only for proprietary information. Effects are firm-level, so they average over workers who did and didn't use the tools. The Ars Technica coverage describes the earlier version.
Chen & Stratton, Harvard (job market paper); coverage in Ars Technica
655
Firms
MerciYanis rewrites its whole platform, about 250,000 lines across 10 repositories, in one day with one engineer and around 30 parallel agents
MerciYanis · Tool unstated
CaveatsWritten by the company's own CTO. The one day excludes the earlier work raising test coverage from an average of about 60% to 100%, which the post says took most of the time. Results are reported from the QA environment; no production figures. Coding tool not named. Stack not stated; the post's code sample looks like TypeScript and its diagram names PostgreSQL and Kafka, so check before filling it in.
Roughly 250,000 lines across 10 repositories
Scope
Repo fixer: a scheduled CircleCI pipeline with LLM fixers opens 150 migration PRs across an org overnight and keeps fixing new repos
Claire Alvis (Confident Commit) · repo fixer
CaveatsSelf-reported. The post does not name the employer, the LLM or coding agent used for fixes, or merge rates for the 150 PRs. The Claude skills are for managing the system, not necessarily for the fixes.
150 open PRs across the org by the next day
Migration PRs
Meta's small Forum team builds a new Groups app from scratch with agents running the build-test loop, reaching feature parity in eight weeks
Meta · Tool unstated
CaveatsMeta's own engineering blog. It names no agent, model or vendor, and gives no team size, cost, PR counts or code volume. 'Feature parity in eight weeks' has no pre-agent baseline to compare against.
Core feature parity with Facebook Groups in eight weeks
Time to feature parity
Two engineers and a coding agent move a 41,000-line .NET Framework 4.8 service to .NET 8 in 11 working days, against a 7 to 9 engineer-week estimate
Lamplit Labs (Manish Tiwari) · Tool unstated
CaveatsSelf-reported by the team. The post does not name the coding agent or model. No cost figures. The author notes that the clean record of agent code says more about the gates and ported tests than about the agent.
41k-line .NET Framework 4.8 service
Codebase
ESEM 2026 study of 669 developers: after adopting coding agents they write longer PR descriptions and test more, with no drop in effort
Muhammad Hamza, Dominik Siemon and Wardah Naeem Awan (ESEM 2026) · Tool unstated
CaveatsDrafted from the abstract only. Uses the same AIDev dataset as two existing MSR 2026 stories. Measures developer behaviour, not delivered software.
669 across 103 repositories, plus 228 controls
Developers studied
Juno merges 26 of its last 30 PostHog self-driving PRs, a roughly 90% merge rate, with the CEO still reviewing each one
Juno · PostHog self-driving, PostHog scout
CaveatsVendor-published PostHog customer story promoting PostHog self-driving, the product PostHog sells; the page has no author byline. Figures are self-reported by Juno CEO Marshall Gould. Roughly 90% and 26 of the last 30 describe a recent window, not a total volume, a time period, or a share of all Juno PRs. No calendar duration, cost or total merged-PR count is given. Gould still reads every PR, sometimes edits them, and often tests on a simulator; he has not turned on auto-merge. Some bugs cannot be reproduced easily because they depend on device state such as charging or low power mode. The page does not name the underlying coding model or a catalogue coding agent. "Fixed dozens of other issues" is PostHog's uncounted wording; the "Log all" medication-log example is described as Juno adding a feature after PostHog identified friction, without an explicit statement that self-driving authored that PR.
Roughly 90%
Self-driving PR merge rate
LinkedIn's multi-agent AI code reviewer runs 79,000 reviews a week with 63.9% of suggestions accepted
LinkedIn · Tool unstated
CaveatsBuilder-written. The models and harnesses behind the subagents are not named. This is review of code, not agent-written code; acceptance was judged by an LLM evaluator on a 7-day sample.
79,000+ across 40,000+ PRs in 7,500+ repositories
Weekly reviews
Vercel's AI SDK software factory authors 25–35% of merged PRs and closes most issues, four weeks into production
Vercel · ai-sdk-factory (Vercel)
CaveatsSelf-reported by Vercel, which sells the Sandbox, Functions, Queues and Blob products the factory runs on and promotes a one-click deployable version, so this is vendor-published. The post does not name which coding agent or model powers the factory's agents (it mentions Opus 4.6 only as the trigger for the PR surge), so the tool is Unstated. Results cover just over four weeks. The intro says the factory closes 70-80% of issues while the results section says over 75% of closed issues in July; these are shares of closed issues, not of all open issues. No absolute PR counts are given. The open-issue drop is not attributed solely to the factory.
25–35%
Share of weekly merged PRs authored by the factory
DoorDash's in-house Flux cloud agent platform automates 130,000 engineering tasks in a month
DoorDash · Flux (DoorDash), Agent Gateway (DoorDash)
CaveatsPlatform post from the builders. Which coding agent harnesses Flux runs is not named. Counts are usage volumes; no merge rates, quality or time-saved figures are given.
130,000 in a single month
Engineering tasks automated
Wix's Code Migration Platform has a coding agent open migration PRs across hundreds of repos, saving 650 developer-days in a quarter
Wix · Code Migration Platform
CaveatsSelf-reported. The days-saved figure is calculated from services affected times estimated manual time per service, compared with actual time. The post does not name the coding agent or models, and says scripts handle a significant share of migrations without an LLM.
650 in a single quarter (their estimate)
Developer-days saved
CMU and Stanford study of a company's "2x" AI mandate: merged PRs per engineer doubled, and automated review overtook human review
Carnegie Mellon University and Stanford University · Tool unstated
CaveatsOne anonymous company. Adoption was not randomly assigned, so the authors avoid exact causal attribution. The abstract does not name the AI tools.
802 developers, 196,212 pull requests (Jan 2024 to Apr 2026)
Sample
Atlassian's Jira team migrates 100+ GraphQL fetchers off a legacy gateway in a week, about two quarters of work, using agents driven by Jira specs
Atlassian · Tool unstated
CaveatsSelf-reported on Atlassian's own blog, and the post doubles as a pitch for Jira as agent infrastructure. It names no agent, model or vendor, and gives no line counts, cost, defect or rollback numbers. The two-quarters figure is the team's estimate of manual effort.
100+ GraphQL fetchers
Scope
Bloomberg's Pomona agent opens one tiny code-quality PR a day, and 32 of 39 were merged with a median close time of just over two hours
Bloomberg (with University College London) · Pomona
CaveatsIndustrial experience paper by Bloomberg engineers and UCL researchers about their own tool, one team, small sample. The paper says it cannot reveal which AI services or models were used, and data and code are not released.
39 over 55 workdays; 32 merged (82.1%)
PRs
Dropbox’s internal coding agent platform Nova accounts for roughly 1 in 12 pull requests, and runs flaky-test fixes and migrations
Dropbox · Nova, Deflaker
CaveatsWritten by Dropbox engineers. The 1 in 12 figure comes from the DX Annual write-up and has no date range or merge rate attached; the Nova introduction post gives no output numbers. Dropbox does not name the coding agents Nova runs today, only that it supports several; the earlier migrator was Goose-based.
Roughly 1 in 12 pull requests at Dropbox
Share of pull requests
Stripe builds continuous Java upgrades with Minions fixing CI failures, reaching 93%+ of services on JDK 17 within a week of rollout
Stripe · AutoJDK, Minions
CaveatsMuch of the work is deterministic build-graph automation; agents handle a subset of failures. The post doesn't say how many fixes came from Minions or which model they use.
93%+ of services within under a week of rollout
JDK 17 adoption
Plaid’s Hamilton cloud coding agent writes thousands of PRs and accounts for about 20% of all merges
Plaid · Hamilton
CaveatsSelf-reported. Commercial coding harnesses are not named (tools left Unstated; Hamilton is internal). The 20% merge share and “thousands of PRs” lack absolute denominators. Sister adoption post is a secondary URL for company-wide context.
Roughly 20% of all merges
Hamilton share of merges
Google migrates production YouTube models from TensorFlow to JAX with a planner, orchestrator and coder agent system, 6.4x to 8x faster than by hand
Google (AI and Infrastructure) · Tool unstated
CaveatsGoogle writing about its own system; it also sells AI products. The post does not name the coding model or say how many models were migrated. Speedup is from their evaluations; a technical paper is referenced but not linked here.
6.4x to 8x over manual migration
Speedup
MSR 2026 study: coding agents give open-source repos a velocity bump only as their first AI tool, but lasting technical debt either way
Shyam Agarwal, Hao He, Bogdan Vasilescu (MSR 2026) · Tool unstated
CaveatsObservational, open-source repos only, and a Mining Challenge paper on one dataset. Adoption is inferred from the first agent-authored PR, so earlier unlabelled AI use is missed. Replication package: github.com/shyamagarwal13/agentic-coding-impact.
+36.3%
Commits (agents as first AI tool)
Vercel auto-merges 58% of PRs in its largest monorepo without human review, cutting average merge time from 29 hours to 10.9
Vercel · Vercel Agent, LLM PR risk classifier (Vercel), Vercel AI Gateway
CaveatsVendor-published: Vercel sells Vercel Agent and AI Gateway, which run the workflow. Dead original link: the original vercel.com address (https://vercel.com/blog/58-percent-of-prs-in-our-largest-monorepo-merge-without-human-review) now returns 404 and is not in Vercel's sitemap, so this story links to the Wayback Machine copy of 7 April 2026 (checked 10 November 2026); all numbers were verified from that archived copy, which shows no author names. The source covers an LLM classifier plus auto-approval, not a coding agent writing the code: it does not say which agents (if any) authored the PRs, and it does not name the classifier model (secondary write-ups say Gemini). Self-reported, from an experiment window of unstated length, in a repo dominated by marketing, docs and UI changes, so transfer to riskier codebases is unproven. The control group had 2 reverts out of 513 reviewed low-risk PRs. Cost figures are per-assessment rates, not a total.
58%
PRs merged without a human reviewer
Taller Technologies’ Chiron platform cut three modernization programs from 36 to 9.3 summed project-weeks, with gains coming only once agents were orchestrated
Taller Technologies · Chiron
CaveatsBoth authors are executives at the company that built Chiron and disclose the conflict of interest. The benchmark was assembled retrospectively from engineering records and practitioner recall, in one organization, with no independent audit. Person-day figures are modeled from staffing assumptions, not logged hours. Models and coding tools are not named.
arXiv (Maximiliano Armesto and Christophe Kolb, Taller Technologies)
36.0 weeks (traditional) to 9.3 weeks (V4), 3.87x faster
Summed project duration
METR's late-2025 follow-up: raw data hints at speed-up, but developers refusing to work without AI breaks the study
METR (57 open-source developers) · Tool unstated
CaveatsMETR itself calls this very weak evidence because of selection effects; pay was also reduced from $150/hr to $50/hr.
57
Developers
Instacart's Caper team migrates its smart-cart Android app to Jetpack Compose with AI, 5-7x faster on navigation
Instacart · Tool unstated
CaveatsNo coding tool or model is named. Speed-up and hours saved are estimates for Phase 2 only; Phase 3 was still in progress and Phase 4 had just started when published.
5-7x
Phase 2 speed-up
Uber's uReview AI code reviewer covers over 90% of ~65,000 weekly diffs, with 75% of comments rated useful
Uber · uReview (Uber)
CaveatsSelf-reported by Uber. This is an AI code reviewer, not an agent that writes code, and the post gives no merge-rate, cycle-time or defect outcomes. It does not say which coding agents authored the reviewed diffs, so the tool is Unstated. Published August 2025, earlier than Uber's other stories on the site. Volume figures are inconsistent: '~65,000' diffs is called weekly in one place and 'per month' in another, and 'over 90%' coverage sits awkwardly with 'over 10,000 commits' processed a week. The 1,500 hours a week is an estimate assuming a second human reviewer needs 10 minutes per commit. The usefulness rate counts only engineers who rate comments. Fixer, the companion tool that proposes code changes, is not covered.
Uber Engineering blog (Sonal Mahajan, Shauvik Roy Choudhary, Will Bond)
Over 90% of ~65,000 weekly diffs landed
Coverage
Airbnb migrates ~3.5K Enzyme test files to React Testing Library in 6 weeks with LLMs
Airbnb · Tool unstated
CaveatsModel names and dollar cost not disclosed. Published date is approximate (March 2025, per InfoQ coverage).
~3,500
Test files migrated