What the Best Engineers Built for Their Coding Agents

About this episode

What happens when coding agents see your entire system: code, services, infrastructure and live traffic, all connected? Most agents are blind to everything outside the repo. Adyen Staff Engineer Mat Jones explains what changed once theirs weren't, and why he calls it somewhat scary. In this video, we cover: • Running five or six coding agents in parallel with git worktrees and Atrium, an internal tool that lets agents coordinate and share memory • Architect: nine connected graphs in Neo4j covering services, code, DNS, data stores and infrastructure • Ingesting 7 million trace spans a second with Kafka and Apache Flink, and what collapsed on the first try • Sentinel: anti-pattern monitoring, with agents that raise the fix as a merge request • MCP vs APIs vs CLI tools, and how to deal with tool bloat This episode is for software engineers and platform teams who want coding agents to reason about real systems, not just the repo in front of them. You'll leave with a concrete place to start and an honest view of the risks. 00:00:00 - Intro 00:00:42 - Running Five Coding Agents in Parallel 00:01:35 - Atrium: How Agents Avoid Stepping on Each Other 00:06:57 - Why Graphs Save Codi