Why We Built Our Own Background Agent — Ramp Builders Blog
builders.ramp.com · 2,817 words · saved by 5 readers
The craft of engineering is rapidly changing. We built our own coding agent to accelerate faster.
January 12, 2026 We built our own background coding agent: Inspect. Inspect writes the code like any other coding agent, but closes the loop on verifying its work by having all the context and tools needed to prove it, as a Ramp engineer would. For backend work, it can run tests, review telemetry, and query feature flags. For frontend, it visually verifies its work and gives users screenshots and live previews. Agents should have agency, and so we made sure Inspect is never limited by missing context or tools, but only by model intelligence itself. Each session runs in a sandboxed VM on…
saved by
related reading
- Effective harnesses for long-running agents \ Anthropicanthropic.com
- Best practices for coding with agents · Cursorcursor.com
- Ramp: Agentic Workflow Automation for Financial Operations - ZenML LLMOps Databasezenml.io
- LangChain: the open agent platform to own your intelligencelangchain.com
- Building Spectre: Internal Collaborative Cloud Agent Platform | Harveyharvey.ai
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- Towards self-driving codebases · Cursorcursor.com
- Introducing FrontierCode | Cognitioncognition.ai
- What we’ve learned building cloud agents · Cursorcursor.com
- How we made Ramp Sheets self-maintainingx.com
- Code was our medium for thoughtwattenberger.com
- One Developer, Two Dozen Agents, Zero Alignmentmaggieappleton.com