OpenCode case studies: 6 sourced stories
Stories using OpenCode. Of the 6 stories, 6 by the people who did the work. 4 involve an existing codebase and 1 started from scratch. Every number links to where it was published.
Zalando's 2.5 years of agentic engineering across 250+ teams: a risk-based bot auto-approves 33% of PRs and cuts their lead time 20-40%
Zalando · GitHub Copilot, Claude Code, OpenCode
CaveatsWritten by Zalando's own engineering leadership. The 20-40% lead-time cut is for auto-approved PRs compared with all PRs. No productivity or cost totals; complexity findings come from four example codebases. Also mentions pi, a coding agent not in the site's tool list.
More than 250 engineering teams
Teams
PSI, EPFL and Max Planck researchers translate the ORB5 plasma simulation code from Fortran to C++/Kokkos with Cursor, Claude Code, Codex and OpenCode, matching the original to near machine accuracy
ORB5X (PSI, EPFL, Max-Planck-Institut für Plasmaphysik) · Cursor, Claude Code, OpenCode, OpenAI Codex
CaveatsWritten by the researchers who did the translation. The paper gives no code size, duration, cost or share of code written by agents. The tuned Fortran ORB5 is still faster than ORB5X where it runs; the authors present ORB5X as an initial implementation, and some routines still stage through host memory for FFTW, HDF5, LAPACK and MPI. The strong-flow path should not be treated as production-ready until a rotating-plasma case is validated.
Almost machine accuracy for ITG, ITPA and chirping field components
Benchmark agreement with Fortran ORB5
Cloudflare’s OpenCode-orchestrated AI code review runs 131k times across 5,169 repos in 30 days, median 3m 39s and $0.98
Cloudflare · OpenCode
CaveatsSelf-reported Cloudflare engineering blog. This ships an AI review system, not application features; merge-quality impact beyond break-glass rate is not measured. Model names and costs are as of the March–April 2026 window.
131,246 review runs on 48,095 MRs across 5,169 repos
30-day volume
Eve’s Slack-driven background agent WALL-E authors 22% of merge requests in its monorepo, 53% of them one-shot
Eve (Eve Legal) · OpenCode, WALL-E
CaveatsWritten by Eve’s own engineer. The post gives no absolute counts of merge requests, team size, cost or time period, and does not name the models used. One-shot means no human iteration before the merge request, as defined by Eve.
22% of all merge requests in the monorepo
Share of merge requests
Cloudflare engineer rebuilds the Next.js API surface on Vite in under a week with Claude in OpenCode, for about $1,100 in tokens
Cloudflare · OpenCode
CaveatsWritten by the engineer who did the work, on the company blog, at launch. vinext is labelled experimental and "not yet been battle-tested with any meaningful traffic at scale". Benchmarks use a single 33-route app and measure compilation and bundling, not serving performance; the post says to treat them as directional. Static pre-rendering at build time was not supported at launch. The post says some AI PRs "were just wrong" and needed regular course correction. Exact model versions are not named.
Under a week; first commit 13 February
Time
Ramp's in-house background agent Inspect writes about 30% of merged PRs in its frontend and backend repos, without a mandate
Ramp · OpenCode, Inspect (built on OpenCode)
CaveatsCompany writing about its own tool. No figures for PR size, review effort, defects or cost. Says it supports all frontier models without naming which ones are used most.
About 30% of PRs merged to frontend and backend repos written by Inspect
Share of merged PRs