flâneur

X

x.com · 1,019 words · saved by 1 readers

Don’t miss what’s happening People on X are the first to know. Log in Sign up How we made Ramp Sheets self-maintaining Ramp Labs @RampLabs · 1h · Follow 6 9 71 6.8K We built an agentic system to maintain Ramp Sheets. It continuously monitors production, triages alerts, and pushes fixes without human intervention. The system runs on a thousand AI-generated monitors, one for every 75 lines of code. We built this because: Agents are cheap to run, infinitely patient, and easy to parallelize. These properties make exhaustive monitoring feasible at production scale. Teams hate owning observability, ourselves included. Offloading this grunt work to an agent lets us ship faster. Strong observability and QA mean fewer bugs, less downtime, and a better experience for Ramp customers. Ramp Inspect We chose to build our maintenance system using Ramp Inspect, our internal background coding agent. Each Inspect session spins up a full sandboxed dev environment, allowing the agent to make real API requ

We built an agentic system to maintain Ramp Sheets. It continuously monitors production, triages alerts, and proposes fixes without human intervention - although no code is merged without engineer review. The system runs on a thousand AI-generated monitors, one for every 75 lines of code. We built this because: Agents are cheap to run, infinitely patient, and easy to parallelize. These properties make exhaustive monitoring feasible at production scale. Teams hate owning observability, ourselves included. Offloading this grunt work to an agent lets us ship faster. Strong observability and…

saved by

related reading