Ramp engineer Zach Bruggeman describes how Inspect’s shared sessions changed collaboration in this 14-minute AI Engineer talk.

Give everyone a strong starting point

  • Inspect runs remotely with multiplayer sessions and shared integrations for code, telemetry, databases, and work tracking.
  • Ship effective defaults centrally so each developer avoids repeating setup and discovering the same improvements alone.
  • Bruggeman says adoption grew without a usage mandate; Inspect remained an available baseline alongside personal tools.

Make the work visible

  • Sessions are visible within Ramp by default, so colleagues can learn from prompts and tool use in existing channels.
  • Attach the conversation, tool results, screenshots, and browser-verification videos to the change being reviewed.
  • The Inspect team learns from unexpected uses and turns recurring patterns into built-in capabilities.

Let skeptical colleagues join the investigation

  • In Bruggeman’s debugging story, Inspect initially blamed newly added telemetry, prompting understandable skepticism.
  • Further investigation found an exporter calling fetch without reading or cancelling the response body.
  • An explicit response-body cancellation fixed the reported errors in Ramp’s deployment.
  • Keeping the investigation in a shared thread let the bug reporter contribute and suggest new uses for Inspect.

Let other teams extend the platform

  • Two engineers built Review Buddy using Inspect’s existing pull-request triggers and coding capabilities.
  • Their extension pushed the core team toward a broader development workflow.
  • Bruggeman reports that Inspect writes and ships around 75% of Ramp’s code; the talk leaves the counting method unspecified.
  • Caveat: These are Ramp’s adoption claims and case studies; they do not measure company-wide productivity or prove every generated change correct.

“Build tools that kill information silos.” — Zach Bruggeman, 3:06