quality_assurance · finance · workflow
Ramp builds a full-context background coding agent on Modal that writes over half of all merged pull requests
Ramp wanted to give every builder—engineers, product managers, and designers—access to AI-assisted coding, but local agents required dev environment setup, couldn't integrate with internal tooling, and any background agent slower or less capable than local would not get adopted.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Cron filesystem snapshot build
Every 30 minutes, a Modal Cron clones repositories, installs dependencies, runs initial builds, and saves a filesystem snapshot.
Tools used
ModalModal SandboxesOpenCodePostgresRedisTemporalRabbitMQGitHub · partnerSlack · partnerBuildkite · partnerSentry · partnerDatadog · partnerLaunchDarklyChromium
Outcome
Within a couple of months, roughly half of all merged pull requests at Ramp are started by Inspect, and over 80% of Inspect itself is now written by Inspect, with product managers and designers empowered to ship code directly.
Results
Time saveda few seconds
Volumeover 80%
Grounding & classification
Source type: vendor customer story
38 fields verified against source quotes.
agentic workflowai agentcode generationcomputer visionmulti agent workflowcode diff prknowledge basemetric backednamed customerproduction runtime claimedtools describedworkflow describedfinancial servicesautomation rateemployee productivitythroughput increasevendor customer storyquality assuranceagentic task executionai draft human approval