The AI Record
We have on-call assistant that begins investigating the moment an incident is declared. We have Testo, a QA-focused agent. Our data team built Ramp research, creating an entirely custom tool set for the agent that's built on top of Inspect's access to our data warehouses. Our product operations team built Voice of the Customer, which synthesizes feedback from all the sources we have access to and compiles reports for teams. These, along with 200 other custom agents, all run on the Inspect's platform.

Zach BruggemanPrincipal engineer, Ramp · Practitioner, Ramp

Context. Bruggeman lists agents that teams at Ramp built on the Inspect platform.

Talk: @Inspect fix this | Zach Bruggeman Principal Software Engineer at Ramp, Runtime 2026, Modal (YouTube), November 2, 2026, at 07:16.

  • 200 agents custom agents, as described in 2026

Checked against the source [ Grade B ] Said in the last year Ramp: $1.5 billion revenue, annualized revenue (ARR), by early June 2026

Filed under

Who is speaking

Zach Bruggeman, Principal engineer; founding engineer of Inspect. Built the tool Bruggeman writes about, so Bruggeman knows how it is used; Bruggeman is also an employee describing the company's own tool.

How this was checked

Checked against the source by a first reader, then confirmed independently by a second reader who fetched the source without seeing the first reader's notes (Independent review agent (Claude Sonnet), blind second pass from passage text and citation only, no repository access, 2026-11-05).

The words are in whisper lines 193-204. Whisper has 'RAMP research', and the passage reads 'Ramp research', a casing difference only. '200 other custom agents' appears verbatim. The passage's 'Inspect's platform' also matches.

How to cite this passage

Zach Bruggeman (Ramp), “@Inspect fix this | Zach Bruggeman Principal Software Engineer at Ramp, Runtime 2026”, Modal (YouTube), 2026-11-02, at 07:16. https://www.youtube.com/watch?v=VTu6wAKgiwY Archived at https://the-ai-record.com/passages/ramp-on-call-assistant-begins-investigating-moment-incident-2026

More from the same source

We have a dumb but effective approach. Every 30 minutes, we clone every repository, install all of its dependencies, and do any initial setup, and then take a file system snapshot. Then when a new inspect session is created, we start the sandbox from that snapshot, and the sandbox starts up in just a couple seconds from that exact file system state. This means when you send a prompt, you're not waiting on Git or npm or really anything, it just starts the sandbox and begins processing your prompt.

Zach BruggemanPrincipal engineer, Ramp · Practitioner, Ramp

Context. Bruggeman explains how Inspect sandboxes (run on Modal) start quickly from file system snapshots.

Talk: @Inspect fix this | Zach Bruggeman Principal Software Engineer at Ramp, Runtime 2026, Modal (YouTube), November 2, 2026, at 03:23.

  • 30 minutes snapshot interval, as described in 2026

Checked against the source [ Grade B ] Said in the last year Ramp: $1.5 billion revenue, annualized revenue (ARR), by early June 2026 Passage page

Inspect is Ramp's in-house team-based coding agent. It lives in Slack, GitHub, our own web interface in every Ramp Links Chrome, linear, and more. It works fully remotely, spawning a sandbox powered by modal with an entire Ramp development environment for each session. … spin up in under five seconds and are set up with all the dependencies and connections you need to let you prototype, build, verify, and ship your work.

Zach BruggemanPrincipal engineer, Ramp · Practitioner, Ramp

Context. Opening of Bruggeman's talk at Modal's Runtime 2026 conference, describing Inspect, Ramp's internal coding agent.

Talk: @Inspect fix this | Zach Bruggeman Principal Software Engineer at Ramp, Runtime 2026, Modal (YouTube), November 2, 2026, at 00:18.

  • 5 seconds session start time, as described in 2026

Checked against the source [ Grade B ] Said in the last year Ramp: $1.5 billion revenue, annualized revenue (ARR), by early June 2026 Passage page

We've run almost three million sessions with it. To give an idea of the growth curve this has resulted in, in December, before the holidays, Inspect was writing around 10% of merged … requests across all of Ramp. That jumps to roughly 30% around the start of January, and then around 50% at the end of January, and today it's about 75%.

Zach BruggemanPrincipal engineer, Ramp · Practitioner, Ramp

Context. Bruggeman describes Inspect's growth from a side project. Years are inferred from his references to 'last year' and December/January; the talk was published 2026-11-02.

Talk: @Inspect fix this | Zach Bruggeman Principal Software Engineer at Ramp, Runtime 2026, Modal (YouTube), November 2, 2026, at 05:28.

  • 3 million sessions sessions run, to 2026-11 ('almost')
  • 10% ai share merged prs, December 2025, before the holidays. Level not stated
  • 30% ai share merged prs, around the start of January 2026. Level not stated
  • 50% ai share merged prs, end of January 2026. Level not stated
  • 75% ai share merged prs, 2026-11 ('today'). Level not stated

Checked against the source [ Grade B ] Said in the last year Ramp: $1.5 billion revenue, annualized revenue (ARR), by early June 2026 Passage page

But what was really crazy about this is that at no point did we ever have a mandate for people to use Inspect. This was just a natural growth curve in the company, built from people watching others use Inspect successfully. Even today, there's still no mandate. That's the reason it's not 100%, and frankly, we aren't aiming for that.

Zach BruggemanPrincipal engineer, Ramp · Practitioner, Ramp

Context. Follows his statement that Inspect writes about 75% of merged pull requests at Ramp.

Talk: @Inspect fix this | Zach Bruggeman Principal Software Engineer at Ramp, Runtime 2026, Modal (YouTube), November 2, 2026, at 05:59.

Checked against the source [ Grade B ] Said in the last year Ramp: $1.5 billion revenue, annualized revenue (ARR), by early June 2026 Passage page

Our most successful example of this has been review buddy, our code review agent. It started with engineers on another team hooking up a GitHub webhook to Inspect's API with a review-oriented prompt. They could just focus on making the code review part great while we provided them all the infrastructure to actually run this agent. Now, review buddy runs on every pull request at Ramp, and we've replaced all of our third-party code review tools.

Zach BruggemanPrincipal engineer, Ramp · Practitioner, Ramp

Context. Bruggeman describes Review Buddy, a code review agent built on Inspect's API and platform.

Talk: @Inspect fix this | Zach Bruggeman Principal Software Engineer at Ramp, Runtime 2026, Modal (YouTube), November 2, 2026, at 06:52.

Checked against the source [ Grade B ] Said in the last year Ramp: $1.5 billion revenue, annualized revenue (ARR), by early June 2026 Passage page

Something wrong? Report a correction. JSON: /api/v1/passages/ramp-on-call-assistant-begins-investigating-moment-incident-2026.json