Every week the timeline picks a new word, repeats it until it loses all meaning, and dares you to admit you don’t know what it means. This week the word is “loop.” Six letters, everywhere, and almost nobody chanting it can tell you what one is.

So I did what I always do when the timeline starts speaking in tongues. I ran /whathaveimissed on it and read the receipts. The short version: the thing is real, it has a five-year lineage, and the punchline is one I like. The loop, not the model, is now the expensive part.

The tweet that started the bar fight

Peter Steinberger posted one sentence on June 7. The tweet blew up and the replies turned into a bar fight.

“Here’s your monthly reminder that you shouldn’t be prompting coding agents anymore. You should be designing loops that prompt your agents.”
— @steipete, June 7, 2026

Varadh Jain asked the only honest question in the thread: what does this look like in practice? Matthew Berman’s reply became the mood of the whole discourse.

“nobody knows but him and boris.”
— @MatthewBerman, June 7, 2026

That’s the state of play. The loudest idea in AI coding goes viral while the people retweeting it argue about what it means. Peak 2026.

My bias, disclosed: I run a loop every night that opens pull requests across roughly thirty open-source repos while I sleep. So instead of rolling my eyes I read the pile. Fifteen Reddit threads, twenty-one X posts, one pattern. One camp declared prompt engineering dead. The camp with hands on keyboards was more careful.

“It’s not ralph/goal loops, that’s old hat by now. It’s probably some kind of continuous orchestration loop that oversees other threads/agents.”
— @trashpandaemoji, June 7, 2026

That reply is the closest thing to a right answer anyone posted. Remember Trash Panda. We come back to them.

What a loop actually is

Boris Cherny built Claude Code as a side project in September 2024. It now sits behind close to four percent of all public commits on GitHub, which is a deeply normal thing to do with a side project. On stage at WorkOS Acquired Unplugged on June 2 he gave the cleanest definition you’ll find.

“Now it’s actually leveled up, I think, again, to the next wave of abstraction where I don’t prompt Claude anymore. I have loops that are running. They’re the ones that are prompting Claude and figuring out what to do. My job is to write loops.”
— Boris Cherny, WorkOS Acquired Unplugged, June 2, 2026

Plain version: a loop is a small program that prompts the coding agent for you, reads what came back, decides whether it’s done, and if not, prompts again. You stop being the thing inside the loop typing prompts at 11pm. You become the author of the loop. The model becomes a subroutine.

Boris tells it as three stages, and finding yourself on his ladder is the fastest way to get it. A year ago he wrote code by hand with autocomplete, like a peasant. Then he ran five to ten Claude sessions in parallel and prompted each one. Now he prompts none of them. He writes the loops, and a couple hundred agents read his GitHub, Slack, and Twitter and decide what to build next. Before you file that under LinkedIn fantasy, he has the receipt.

“In the last 30 days, 100% of my contributions to Claude Code were written by Claude Code. I landed 259 PRs.”
— Boris Cherny, via Simon Willison, December 27, 2025

He deleted his IDE in November and hasn’t opened it since. Now, the nuance the “prompt engineering is dead” crowd sprints straight past: he is not saying engineers are obsolete. Someone still decides what to build, talks to customers, and keeps the teams pointed the same way. He says good engineers matter more than ever. The job didn’t disappear. It went up an altitude. You used to write the code. Now you write the thing that writes the code.

Five things hiding in one word

The replies were a mess because “loop” carries at least five different things. Here’s the ladder, oldest to newest, so people can stop talking past each other.

Stage one is the academic while-loop. The 2022 ReAct paper wrote it down: the model reasons, calls a tool, reads the result, repeats until done. One model, one loop, a human watching the whole time.

Stage two is AutoGPT in 2023. Same idea with a goal and permission to prompt itself. It became famous for spinning forever while accomplishing nothing, and that single failure mode bankrolled two years of “agents are a toy” takes.

Stage three is the one Trash Panda called old hat: the ralph loop, published by Geoffrey Huntley in 2025. It is almost rude how simple it is, a bash one-liner that pipes the same prompt file into the agent over and over. The actual innovation was discipline, not cleverness: every iteration resets the context to a fixed set of anchor files instead of letting the conversation bloat. Huntley ran one for three months and got a working programming language out the other side. Teams at a YC hackathon used the same trick to ship six repos overnight for about 297 dollars in API calls, which is less than most teams spend deciding not to.

Stage four productized that. In spring 2026 both Codex and Claude Code shipped a /goal command that runs the ralph loop until a small validator model agrees the task is done.

Stage five is what Boris and Steinberger actually mean, and it’s new, not rebranded. Four things changed. The loop became the unit of work, not the task. Loops started supervising other loops, in parallel and on a schedule. Scheduling replaced the human kickoff, so the loop runs on infrastructure time instead of your attention span. And durability got serious, with git-backed state and crash recovery, because a thing that runs for two days has to survive a restart. Ralph assumed your terminal stayed open. The 2026 version assumes it doesn’t. So Trash Panda was right twice: single-agent ralph is old hat, and the multi-agent orchestration loop sitting on top of it is the actual new thing.

It’s just a cron job with a hat on

The best skeptic line in the whole corpus was four words, posted under someone gushing that loops are the future.

“Cronjobs have funny re-branding rn.”
— X reply, loops discourse, June 2026

This one deserves a straight answer, because it’s half right and half-right is the most annoying kind. Yes, the scheduling layer is cron. Boris literally runs his on cron. The /loop command uses cron under the hood. If your whole definition of a loop is “a thing that runs on a timer,” congratulations, we shipped that in 1975 and you can go home.

What cron never had is the part in the middle. A cron job runs a fixed script. A loop runs a model that looks at the current state, decides what to do next, does it, checks whether it worked, and decides whether to keep going. The decision belongs to the agent, not to you and not to a hardcoded if-branch. Stack those, let one loop dispatch and supervise others, give them durable shared state, and you have something cron cannot express. The honest framing: a loop is cron with a decision-maker in the body, and all the interesting engineering is the fence you build around that decision so it doesn’t walk off a cliff.

What it looks like when you build one

Enough theory. The on-ramp is one line. Claude Code shipped /loop, and Boris’s own example is the canonical starter. Paste this and change the nouns.

/loop babysit all my PRs. Auto-fix build issues, and when comments come in, use a worktree agent to fix them.

A few days later he posted his fuller recipe, five tips for running Opus autonomously for hours or days. In his words: use auto mode for permissions so Claude doesn’t stop to ask; use dynamic workflows so Claude can orchestrate hundreds or thousands of agents; use /goal or /loop to nudge it to keep going until it’s done; run Claude Code in the cloud so you can close your laptop; and make sure Claude has a way to self-verify its work end to end.

Tip five is the one the hype crowd skips and the practitioners can’t stop talking about. A loop is exactly as trustworthy as its ability to check its own work, and not one bit more.

That’s the whole idea in miniature. You didn’t write the steps. You wrote the intent and the stopping condition, and the loop prompts the agent every tick. Even TikTok got this one right, which I did not have on my bingo card.

“Loop mode is one of the clearest signs that AI coding is moving from one-off prompts to background operations.”
— @ai.native.founder on TikTok, June 2026

The deep end is Steve Yegge’s Gas Town, launched in January: twenty to thirty Claude Code instances coordinated by a Mayor agent, with patrol agents running continuous loops and state kept in git so the work survives a crash. That’s the “continuous orchestration loop that oversees other threads” Trash Panda was reaching for, except shipped and open source.

The most practical lesson in the entire pile is boring, which is how you know it’s true: a loop is only as good as its ability to check itself. The fastest-growing sub-theme wasn’t orchestration. It was verification.

“Your coding agent can move fast, but bad commits compound fast too.”
— @DanKornas, June 2026

Kornas is shipping roborev, a tool that reviews every commit in the background and feeds the findings back to the agent while the context is still warm. An open loop that writes code with no feedback is a machine for producing confident mistakes at scale. A loop that writes, runs, reads the result, and corrects is the thing that works. The loop isn’t the magic. The feedback inside it is.

The plot twist: the loop is now the expensive part

Here’s where the research stopped being philosophy and turned into an accounting problem. The sharpest deflation of the whole agents mythology came from a working engineer who was clearly done pretending.

“Every ai agent i shipped this year is a for-loop, an llm call, and a try/catch around the json parsing. The only thing agentic about it is the anthropic bill at the end of the month.”
— @rohit_jsfreaky, June 2026

That bill is not a joke. Receipt of the month: Uber capped its engineers at 1,500 dollars per person per tool per month for Claude Code and Cursor after burning its annual AI budget in four months. Once the model writes the code for almost nothing, the money moves to the loop running it.

“The costliest thing in AI coding is no longer writing code, it’s managing the agent loop.”
— @runes_leo, June 2026

And the nightmare everyone in production has already met is the loop that won’t stop.

“Without guardrails, you get infinite loops and billing surprises orders of magnitude over budget.”
— @cv_usk, June 2026

Which is why every serious 2026 write-up on loops lands on the same three hard stops: a maximum iteration count, no-progress detection, and a token or dollar ceiling. The romantic version of loops is that you write them and a thousand agents build your company overnight while you sleep. The production version is that you write them, and most of your job is making sure they halt before they expense a small car. Gartner has agentic AI parked at the peak of inflated expectations, with about seventeen percent of organizations actually running agents. The distance between the timeline and the receipts is the real state of play, as usual.

It’s not loops. It’s skills.

Here’s where I land after a week of watching this, and it’s the part nobody’s chanting. The loop is plumbing. The asset is the skill it calls.

Steinberger’s other recurring point pairs with the loops one and is, quietly, the more durable half: if you do something more than once, turn it into an automated skill, and if you do something hard, turn it into a skill afterward so next time is free. A loop with no reusable skills inside it is a while-true wrapped around a stranger. A loop that calls a library of sharp, tested, named skills is a system that compounds. The Reddit practitioner who’s actually converting put it better than the influencers did.

“A lot of people are rolling their eyes on Twitter, but my ears are perked up.”
— r/ChatGPTCoding, June 2026

This is the same shape we see at every bottleneck we work on. The constraint is almost never “do the work faster once.” It’s “capture the work so nobody redoes it next week.” A loop without skills is speed with no leverage, which is just an expensive way to stay busy.

So the answer to “WTF is a loop” is not a hot take about prompt engineering dying. It’s this. Stop being the thing inside the loop. Write the loop once, give it skills worth calling and feedback so it can check itself, cap it so it halts, and let it run on cron while you go decide what’s actually worth building. Steinberger and Boris are describing the same animal from two sides. The only people who truly know what a loop is are the ones who’ve already built one. The good news, as of this month, is that the on-ramp is a single slash command.

Key patterns from the research

A loop is cron with a decision-maker in the body. The model, not a hardcoded branch, picks the next action each tick.

The lineage is real. ReAct in 2022, AutoGPT in 2023, ralph in 2025, /goal in spring 2026, orchestration loops now. Single-agent ralph is old hat. Multi-agent supervision is the new layer.

A loop is only as good as its feedback. Continuous review and validation gates are what make one trustworthy instead of confident.

The expensive resource shifted from tokens to loop management. Cap iterations, detect no-progress, set a dollar ceiling, or meet your new car payment.

The reusable unit inside the loop is a skill, not a prompt. Loops that call sharp named skills compound. Loops that re-derive everything every tick just burn money with conviction.

Compiled from /whathaveimissed runs on 2026-06-07. Facets: designing loops that prompt coding agents, ai loops, coding loops. Sources across Reddit, X, YouTube, TikTok, Instagram, Hacker News, and GitHub. Top voices: steipete, bcherny, runes_leo, rohit_jsfreaky, MatthewBerman.

‍