Here we go again.
A marketing team develops a new phrase. Someone influential says it on a stage. Within a week, it is everywhere. And the minions who don’t fully understand AI run with it. A GitHub repo with a clever name and a five-minute quickstart, you are made to feel guilty for skipping. And running under all of it is that low hum of anxiety, the quiet suggestion that if you are still working the old way, you have already fallen behind.
This month (June 2026), the phrase is loop engineering.
The post that lit the fuse reportedly cleared millions of views in a few days, and the influencers stacked up so fast that searching the term now returns a wall of nearly identical articles. I read a pile of them, so you can skip most of it.
What actually is loop engineering?
Loop engineering, at a practical level, is the practice of designing AI systems that act, evaluate, and adjust to complete tasks in a loop. Think of it more like glorified iterations. A compressed agile framework inside a prompt.
Strip the hype off, and the idea is small. That is how these things usually start, with something real and modest, before the circus shows up.
For a couple of years, using a coding agent meant babysitting it. You typed a prompt, read what came back, typed the next one, on and on. Loop engineering is intended to provide you with a truly hands-off experience. You set a goal, wire up a cycle that finds work, does it, checks itself, and goes again, and you walk off while it runs.
Boris Cherny, the engineer who built Claude Code at Anthropic, said, “I don’t prompt Claude anymore. I have loops that are running.” But note where this is coming from. The first part of the problem is the source of the term. The second part of the problem is that it’s just a term that doesn’t really amount to anything new.
Loop engineering is designed to be a marketing play.
The term of the month
Step back and look at previous terms. Prompt engineering in 2023. Then context engineering, then harness engineering, which had its fifteen minutes late last year. Now loop engineering. Four labels in three years, every one of them circling the same plain activity: here is how you can get a machine to do your work.
A field that has to rebrand the same job every few months is telling. It has run dry on fresh things to say, so it grabs a new word and dresses the old practice up in it. And the practice was always there first. People were running agents in a bare while loop, feeding the same goal against a spec and letting a fresh copy pick up where the last one died, months before anybody slapped a label on it. The trick underneath, think, then act, then look, then go again, is old enough to have grandchildren. The branding shows up last and takes the bow.
What gets to me is less the word than the stampede it sets off. These things continue to drive the infailible ideology of systems that can’t actually do what the industry claims they can do. A few genuinely sharp people notice a real shift; a much bigger crowd notices them getting attention; and within days, everyone has a hot take, a framework, a numbered list, a waitlist for a course. The signal vanishes under people performing viral advertising on behalf of an industry desperate for more users. And the loudest voices tend to work at the companies selling the agents, so the vocabulary moonlights as marketing without anyone admitting it. When the engineer who built Claude Code hands you the word for running Claude in a loop, you are watching a product demo with very good lighting.
The output of the term is the problem
Almost all influencers, around the second paragraph, reach for the same promise. Autonomous. The loop runs itself. The human steps out of the loop entirely.
That promise is a fairy tale and demonstrates once again why the industry's marketing will be its eventual downfall.
A loop has no self. It is a control structure, the same for and while you met in your first week of programming, running until a condition somebody wrote tells it to stop. Autonomy means writing your own rules and answering to yourself. A loop answers to its exit condition, and a person authored that condition, set the iteration, and kept a thumb on the kill switch the whole time. You can scroll to the exact line where a loop ends. Now go find me the line where a person’s intentions end. Only one of those is in the file.
This is one of the best examples of the conflation of “autonomous” and “automation.”
A loop that fires ten thousand times is still just automation. It cannot be, and never will be, autonomous. Reflecting on my earlier definition, the process is an iterative loop, an automated continuous improvement until the output matches the user's expectations.
It is not autonomy in action.
The better writers accept this the moment they describe a loop they actually built. Hendrik Krack walked through one of his loops and then said, “The loop didn’t make those calls, it just made the calls I’d already encoded.” And there is the point. The autonomy story disintegrates into reality when you step through the actual process. The human never left. There was no “hands-off experience.” That is a real change in where the effort lives. It is also the plain definition of automation, a word we have had since before any of us were born.
I have always said that AI is powerful. They have incredible capabilities. Build them, lean on them, but we seriously need to get past the glorified buzzwords and get more grounded in reality.
The conflation of automation with autonomy
The phrase “autonomous agent” is, when you stop to think about it for more than three seconds without the aid of strong drink or venture capital, one of those magnificent oxymorons that the universe occasionally permits purely for its own amusement. Autonomy suggests self-governance, intrinsic will, and independence from external control, qualities no computational system can claim. These processes are fundamentally dependent. They require external initiation, data streams, runtime environments, power sources, and human-defined objectives. To call them autonomous is to engage in anthropomorphic sleight of hand, projecting agency onto sophisticated macros that operate within strict boundaries they neither create nor escape.
The problem compounds with loop engineering and specifically the other wrong term, "autonomous loop." A loop is an empty control structure that usually includes a for, while, or recursive pattern lacking any inherent self. It possesses no persistent identity, no unified awareness, and no capacity for independent goal formation. Loops do not originate; they repeat what is imposed upon them. Describing such a mechanism as autonomous creates a deeper absurdity: it attributes selfhood and independence to something that, by definition, has neither. This is equivalent to seeking out a pet rock and calling it living. A "living rock," which I’m sure you can understand, cannot exist. The rock remains inert, and the loop remains a governed repetition devoid of any intrinsic actor.
AI, Systems, Agents, and now Loops, are not autonomous.
But the word “loop” provides us with one of the clearest examples of the conflation between automation and autonomy.
Such messy language thrives in hype. It inflates expectations while evading the mechanical reality beneath the surface. In technical and popular discourse alike, these terms generate confusion rather than insight, turning precise engineering into metaphorical fog.
Before you buy in
You will run into loop engineering soon, in a deck, a roadmap, a board memo, somebody’s very confident LinkedIn post. Autonomous will be riding shotgun. When it shows up, you only need one question.
Who wrote the conditions?
Whoever answers has the authority in the room. Everything else is the machine lapping a track a person laid down, fast and faithful, until the line a person wrote tells it to quit. That is automation.
It was automation last year under a different name, and it will be automation next year under whatever name comes after this one.
If you find this content valuable, please share it with your network.
Top comments (0)