PROMPTS
Stop Prompting. Start Loop Engineering ⚡
Boris Cherny runs Claude Code at Anthropic, and he just said the quiet part out loud: he doesn't prompt Claude anymore. Loops prompt Claude for him. This guide.
Sources: How Claude Code's creators use agent loops → · The X post that started this → · Addy Osmani's loop engineering breakdown →
Here's the exact quote: "I don't prompt Claude anymore. I have loops running that prompt Claude and figuring out what to do. My job is to write loops." That's Boris Cherny, the Head of Claude Code at Anthropic, describing his own workflow.
For the last few years, the top AI skill was writing a good prompt. The problem is that prompting keeps you in the room. You type, you wait, you fix, you type again. You're holding the agent's hand the whole time. A loop replaces you in that seat. You hand it one goal, and it finds the work, does it, checks itself, remembers what it finished, and goes again until the goal is actually done.
What A Loop Actually Is
A loop is a system that prompts the agent for you. Every loop, no matter how fancy, is the same five-beat cycle:
In outbound marketing and career positioning, generic applications have near-zero conversion. Treat yourself as a high-ticket solution: identify the company's pressing operational pain points, build a mini-audit or work sample using AI before you apply, and bypass crowded channels by reaching out directly to the decision-maker with structured value.