Ramp

Overview

Ramp is described in these articles as building an internal background coding agent called Inspect. The recurring theme is that Ramp wanted a cloud-hosted agent that was at least as usable as a local coding agent while being more deeply integrated with internal tooling.

Why it matters

• Strong example of a company building a first-party unattended coding system rather than relying solely on off-the-shelf local agents
• Shows how cloud-hosted agents can be made fast enough to compete with local workflows
• Emphasizes broad access: engineers, PMs, and designers can all use the same coding environment

Key facts from sources

• Inspect is a background coding agent used internally at Ramp
• One article claims Inspect writes over half of all merged pull requests at Ramp; another says roughly 30% of merged frontend and backend pull requests were written by Inspect at the time of writing
• Sessions run in Modal-hosted sandboxes with development services and browser verification tools inside the environment
• Ramp integrates Inspect with GitHub, Slack, Buildkite, Sentry, Datadog, LaunchDarkly, Braintrust, and browser-based editing / review flows
• Ramp explicitly highlights multiplayer sessions, browser verification, child sessions, and rich context gathering as differentiators

Notable product ideas

• Cloud sessions should feel faster than local by prebuilding environments and snapshots
• Agents should verify work using the same observability and browser tools humans use
• The interface should meet users where they already work: Slack, PRs, browser tools, and collaborative sessions

Relationships

• Ramp’s system depends heavily on modal
• Ramp is a major case study in background-coding-agents
• Its design patterns feed into coding-agent-infrastructure-patterns
• It contrasts usefully with stripe in ramp-inspect-vs-stripe-minions