A quote is spreading on X (Twitter) that Boris Cherny of Anthropic, who built Claude Code, said "I no longer prompt agents." According to the quote post by @0xCodez, he said in a 10-minute talk, "I'm building 'graphs' and 'loops,' and they build my agents for me. Within 3 to 6 months, all of us will be doing graph engineering for agent systems." The post drew 330,000 views and 1,500 likes and became a talking point in the developer community.
Loops Instead of Prompts, and Now Graphs
That Cherny says "I don't prompt Claude directly, I build loops that prompt" is not new in itself. From around June 2026, the remark spread among developers under the term "loop engineering," and he is counted among those who spread the concept together with Addy Osmani and others. What this X post conveys is the next stage: the discussion is moving beyond the loops of individual agents to "graph engineering," designing how multiple agents connect to and depend on each other.
After Prompts, Graphs?
As cases of running dozens or hundreds of agents at once grow beyond a single agent finishing work in a repeating loop, a diagnosis is emerging that the structure connecting them has become the bottleneck. In fact, Cherny has said that at Anthropic, "there are days I manage tens of thousands of agents." It ties into the trend that designing an agent org chart (who takes over what, and when) has become more important than prompting individual agents well.
Start by Drawing Nodes and Verification Loops
If this trend is real, the implication for practice is clear. The time you spent polishing a single prompt should shift to designing dependencies between agents and retry and branching logic for failures. For now, rather than moving on the "standard within 3 to 6 months" timeline as stated, a gradual approach is safer: first try small-scale loop engineering experiments already under way (iterative goal setting, then automatic verification, then retry), and consider a graph structure only when you need to tie several agents together.
It's Not an Official Term
The key phrase in this quote ("graph engineering becomes the standard within 3 to 6 months") and the "10-minute talk" setting come only from the secondhand X quote post. The original X post could not be opened directly because of a login wall, and neither Fortune nor Turning Post, which I cross-checked, confirmed this exact wording or when the remark was made (which conference). The gist of "building loops instead of prompts" and the spread of the term graph engineering itself are backed by multiple outlets, but the exact wording this post quotes and the "3 to 6 months" timeline are unverified, so it is best not to take them as definitive.