The traditional shape of CI/CD assumed humans worked in the inner loop and pipelines policed the outer one. AI coding agents are tearing that geometry apart. When code can be generated in seconds, waiting until a pull request to run validation, tests, code review and standards checks turns the outer loop into a backlog of preventable rework. The pipeline itself becomes the bottleneck — and the bottleneck shows up not just as time lost but as wasted tokens, half-finished features and engineering controls that fall behind the rate of change.
Rob Zuber, CTO of CircleCI, joined Mike Vizard to lay out how that pressure is reshaping CI/CD platform design. Zuber’s read is that CI quality work has to live where the work is actually happening — inside the developer and agent loop — so issues are surfaced and corrected before changes ever leave a working branch. That means pushing validation, testing, agentic review and deterministic guardrails right up against the moment code is generated, rather than catching problems hours or days later in a pipeline run.
Zuber and Vizard dig into what shifting that feedback earlier actually requires under the hood. Agentic review needs deterministic checks it can trust, observability has to extend to agent behavior, and feature flags become a far more central tool when changes are landing at machine speed. DORA metrics still matter, but Zuber argues the leaders are layering token consumption and pipeline efficiency on top to see whether AI is actually compounding throughput or just compounding cost.
The bigger shift is one of control surface. As AI amplifies how much software an organization can produce, the engineering controls around quality, security and release safety have to amplify in lockstep — or the gains evaporate.