Fullscript's Nitro background agent creates 19% of pull requests three months after launch on a decade-old Rails monolith
Fullscript built Nitro, a cloud background agent with Claude Code as its backbone, because off-the-shelf tools didn't fit its self-hosted GitLab, Linear workflow and decade-old Rails monolith with React frontend (millions of lines, 180+ engineers). Engineers mention @nitro in GitLab or assign it Linear issues; each request gets a fresh environment and it opens a PR or leaves review comments. It launched in late October 2025; by January 19% of PRs were created by it and developers voluntarily tagged it to review 45% of PRs. PMs, designers and the CEO (three changes, including a mobile feature) have shipped through the normal review process. One early N+1 fix passed review and caused production 500s and was reverted.
The numbers (as reported)
| Share of PRs created by Nitro | 19% in January 2026, three months after launch |
|---|---|
| Review usage | Tagged as reviewer on 45% of PRs, voluntarily |
| Build time | About half a year from idea to usable |
| Codebase | Decade-old Rails monolith, millions of lines, 180+ engineers |
| CEO contributions | Three changes, including a mobile app feature |
Facts
- Company / subject
- Fullscript
- Tools
- Claude Code
- In-house tools
- Nitro
- Codebase
- brownfield
- Work type
- Company rollout
- Stack
- Ruby on Rails, React, GitLab, Linear
- Published
- 2026-02-03
- Last checked
- 2026-11-10
What the source claims Practitioner (own blog/paper)
Claimed by the builder, writing about their own work. Not checked independently.
- 19% of pull requests created by Nitro three months after launch 19% of PRs
“In January, three months later, 19% of our pull requests were created by this tool”
- Developers voluntarily tag Nitro to review 45% of pull requests 45% of PRs
“developers are voluntarily tagging the agent to code review on 45% of our pull requests”
- Retroactive reviews of past PRs that caused production issues found the bugs
Caveats
Self-reported. No absolute PR counts, merge rates or quality metrics beyond one reverted N+1 fix that caused production 500s. Every PR still needs human review, CI and E2E tests.
More stories by tool: Claude Code
Related topics: Company rollouts and costBrownfield codebases