Anthropic updated Claude Code on June 10–11, 2026 with nested sub-agent support — agents can now spawn their own sub-agents, up to five levels deep. It's a capability detail that sounds architectural until you look at what it means in practice.
Pair it with a stat from Anthropic's own 2026 Agentic Coding Trends Report: 78% of Claude Code sessions now involve multi-file edits, up from 34% just a year ago. AI is no longer suggesting tweaks in a single file. It's making coordinated changes across services, shared libraries, and configuration layers in a single session.
Nested sub-agents extend this further. A single top-level agent can now delegate to specialized sub-agents handling discrete parts of the codebase in parallel, then synthesize everything into a unified output. For teams with microservice architectures or codebases split across many repositories, this means the reach of one AI-assisted session is wider than ever before.
The review problem this creates is concrete. When one session touches an API, a data service, and a frontend SDK, the resulting PRs land in three different repositories. Reviewing them one at a time — which is what navigating individual repo UIs forces you to do — means evaluating pieces without the cross-service context that makes review meaningful.
The Anthropic report identifies a persistent gap: developers use AI in about 60% of their work, but fully delegate only 0–20% of tasks. High-stakes, cross-cutting changes still require human judgment. That judgment degrades when the interface fragments the picture across tabs.
Engineering leaders should treat cross-repo PR visibility as a prerequisite right now, not a roadmap item. As agentic sessions grow longer and touch more services, the teams with the clearest picture of what's moving across their repositories will make the best review decisions.
For teams already managing PRs across GitHub and GitLab — and feeling the friction of distributed, AI-generated changes — Code Board brings every open PR across every repo into one unified, AI-powered board, so the cross-repo context that effective review demands is always visible.
