We spent four months talking to more than 100 tech leads, architects, and senior engineers about how their teams actually use AI. Review time is a real constraint. But the one they kept circling back to was harder to name: control.
The dominant story about AI and code review is a throughput story: agents write faster than any human can read, the PR queue backs up, and the fix is to review faster with better bots, more QA, more automation. Everyone we spoke to feels that pressure. But ask them whether humans are still needed and the answer is a firm yes: people still own the moments that decide quality, setting up how the agents work, writing the spec, and reviewing what ships. It is that last one, review, where the deepest worry sits.
Humans didn't leave the loop. They moved to its edges.
That yes has gotten more specific over the last six months. The fever that peaked after the late-2025 model releases (also known as the Saaspocalypse era) has cooled into a hangover: a few months of uncoordinated AI use that produced years of tech debt. Three moments came back again and again as irreducibly human.
The agentic software factory. Before a line is generated, someone sets up the system the agents work inside: CLAUDE.md and AGENTS.md, the conventions, the rules, the specs format, the skills that standardize the workflows, the CI checks. Someone also keeps auditing the architecture and the codebase as the agents reshape it. It is the same job the tech lead always had, now aimed at agents instead of people. One finding was consistent: teams that let the agents run that structuring themselves backed off. Code files ballooned to thousands of lines, the layout scattered, and past a certain size the agents lost the thread of their own code. Keeping the system legible stayed a human job.
