newsfilter
← Interviews
AI Engineer14 min

How to build an agent that builds the culture — Zach Bruggeman, Ramp

Zach Bruggeman

Conference Presentation, Fireside Chat
  • Ramp Engineering Metrics & Inspect Adoption

    • Approximately 75% of Ramp's total code is now written and shipped using Inspect, the company's collaborative coding agent.
    • Inspect sessions run remotely with full multiplayer capabilities, integrating directly with Slack, Linear, telemetry, and databases.
    • Technical setup for new Inspect sessions can be spun up in under five seconds.
    • Adoption is driven by Inspect serving as a universal, non-mandatory baseline that eliminates the need for individual engineers to maintain custom configurations.
  • Strategic Lessons on Organizational Culture

    • Eliminating Information Silos:
      • Ramp treats tools as organization-wide assets to prevent disparate outcomes caused by uneven knowledge sharing.
      • Improvements to Inspect are implemented centrally; individual users benefit from global updates without requiring explicit action.
      • The company avoids formal "how-to" training sessions, relying instead on a default "work in public" culture where users learn by observing peer sessions.
    • Building Trust Through Transparency:
      • Trust in agentic coding is cultivated by making all sessions, pull requests, and verification flows visible to the entire organization.
      • Reviewers can inspect the exact AI conversation, tool usage, screenshots, and video verifications of verification agents rather than just code diffs.
      • Public visibility of debugging and problem-solving allows non-collaborators to engage with and learn from technical challenges in real-time.
  • Case Study: Collaborative Debugging of Inspect Itself

    • In February, an engineer named Andrew reported a bug in Inspect; the Inspect agent incorrectly blamed its own telemetry instrumentation for the error.
    • The team engaged in a public thread to investigate, moving from skepticism to collaboration without formal ticketing or private silos.
    • Inspect identified the root cause as a Cloudflare platform limitation regarding fetch calls in the OpenTelemetry library that failed to cancel response bodies.
    • Within one hour, Inspect generated a patch to explicitly cancel response bodies, resolving the issue and transforming a skeptical user into an engaged collaborator.
    • The public nature of the incident led to spontaneous ideas for expanding Inspect's capabilities beyond its original scope.
  • Evolution of Product Capabilities via Internal Innovation

    • Engineers Daniel and Frangel built "Review Buddy," a code review agent for Inspect, without requiring formal permission or resources.
    • Review Buddy replaced the need to rotate between various off-the-shelf code review products, demonstrating Inspect's ability to support internal tool construction.
    • The success of internal projects like Review Buddy prompted the core Inspect team to expand the product's definition from a simple coding agent to a broader collaboration platform.
    • These internal contributions validated a "think bigger together" philosophy where the tool evolves based on how the community utilizes it.
  • Future Outlook & Public Availability

    • Ramp aims to shift engineering culture away from "lone wolf" operators toward collaborative, outward-facing development.
    • Inspect is now available externally to the public via inspect.com/aie.
    • An external waitlist is active with rapid processing, prioritizing teams that sign up.
    • Leadership encourages organizations to identify stalled initiatives and build collaborative solutions using available AI models immediately.