Fighting AI with AI — Lawrence Jones, Incident
Skills:
AI Systems Design80%
Incident's AI SRE runs hundreds of prompts per investigation across logs, metrics, traces, and code. When it produces a wrong root cause analysis, there is no tractable way for a human to read through the full trace and find where the reasoning went sideways. Lawrence Jones, founding engineer at Incident.io, describes the moment the team realized they needed AI to debug their AI.
The talk covers three patterns they built. A small CLI lets coding agents read and edit eval YAML files that had grown too large for agents to work with directly, enabling a red-green runbook where the agent writes a failing eval, fixes the prompt, and checks nothing else broke. Their bigger unlock was serializing every UI debugging view as a downloadable file system: drop it into a Claude Code session, describe the bad behavior, and the agent traces through the prompt hierarchy to tell you exactly which prompt to change. For fleet-scale analysis, 25 agents run in parallel each analyzing one investigation, then a second stage clusters the results to surface systemic failure patterns across customer accounts.
Speaker info:
- https://x.com/lawrjones
- https://www.linkedin.com/in/lawrence2jones/
Watch on YouTube ↗
(saves to browser)
Sign in to unlock AI tutor explanation · ⚡30
More on: AI Systems Design
View skill →Related AI Lessons
⚡
⚡
⚡
⚡
From Science Fiction to Reality: Unitree Launches the World’s First Commercial Transforming Mecha
Medium · AI
A3M Router v2.0: Now an OpenAI-Compatible AI Gateway with 39 Providers 🚀
Dev.to AI
6 Principles for Designing a Commercial AI Agent (from SaaStr's live self-autopsy)
Dev.to AI
Anthropic's June 15th pricing reframes Claude Personal AI Assistants
Dev.to · gtapps
🎓
Tutor Explanation
DeepCamp AI