Loop Engineering for agentic AI

Strip away the branding and a Loop Engineering setup is a small autonomous system that does five things on a turn: discovery, handoff, verification, persistence, and scheduling ^[3]. Instead of a human typing the next instruction, an automation triages what needs doing, hands the implementation to an agent, checks the result, writes state somewhere durable, and schedules the next pass. Osmani packages this as five modular blocks - Automations, Worktrees, Skills, Plugins and Connectors, and Sub-agents - that turn a chat session into a standing machine ^[1][6].

The load-bearing idea is not the scheduling, it is the separation of who builds from who judges. Osmani is blunt that 'an independent skeptical evaluator is far more tractable than making a generator critical of its own work' ^[3]. A model grading its own homework tends to pass itself; a separate evaluator agent, or a hard-coded gate the output must clear, is what keeps the loop honest. That single design choice is the difference between an agent that converges on a working result and one that confidently loops forever on broken code.

Here is the irony at the center of the story. Loop Engineering is a method built on the premise that you cannot trust unverified output - yet the thing that made it famous was a wave of near-identical viral posts that never verified their own claims. The same guide was passed around as a '5-page PDF' from 'the engineers behind Claude Code,' an '11-page' or '12-page PDF' from 'a senior Anthropic engineer,' and a '19-page PDF' from 'a senior Google engineer.' The actual essay is Osmani's, roughly 2,500 words, and Osmani is at Google ^[1][3]. Page counts and employers mutated with every repost because nobody checked the source.

The loop shape got scrambled in transit too, circulating both as act-observe-learn-repeat and as Discover-Handoff-Verify-Persist-Schedule. The discourse mirrored the divergence: evangelical threads on X borrowed authority from named figures like Karpathy and Cherny, dev YouTube reframed loops as 'the new prompting method' and the 2026 default workflow, and Reddit split sharply. It is a clean demonstration of exactly the failure mode the method warns about - generation without an independent check produces confident, plausible, wrong output, whether the generator is a language model or a crowd of reposters.

The sharpest pushback is not technical, it is financial. Unattended loops run continuously, and continuous runs consume tokens - which is great business for the companies selling them. The Register reports that Boris Cherny, who created Claude Code at Anthropic, spends upwards of 130,000 dollars a month in tokens ^[2]. Critic Ed Zitron needled the obvious conflict with a single line: 'Does OpenAI bill itself for its token spend?' ^[2].

Reddit's skeptic camp put it less politely, on r/Anthropic, noting that 'people who sell tokens recommend using as many tokens as possible,' and dismissing brute-force iteration as 'try random stuff until it succeeds,' a step backward from deliberate engineering. The Register's editorial bottom line is the same caution dressed as a warning: 'Automate at your peril. If you set an inherently non-deterministic AI model on a task and expect flawless operation, you deserve to clean up the inevitable mess' ^[2]. Even proponents concede the human stays on the hook - Osmani's own line is that 'the loop changes the work, it does not delete you from it' ^[1].

The structural answer is no. The agent loop dates to ReAct in 2022, which paired Reason with Act so the agent observed each result before its next step ^[4]. Reflexion followed in 2023, bolting memory and self-critique onto ReAct so a failed attempt left a verbal lesson in episodic memory for the next iteration ^[4]. Scheduling agent runs on a cron is older still. The Register sharpens the rebrand charge by noting that Karpathy implemented AI loops months before the viral posts that supposedly introduced the idea ^[2].

What is genuinely new is not the loop but the tooling that finally made unattended runs practical: slash-command loops, cron scheduling, hooks, worktrees, codified skills, MCP connectors, and sub-agents reached maturity together ^[1]. That is the honest version of the claim - Loop Engineering is less a discovery than a name for a workflow that the 2026 generation of agent tooling made accessible to people who are not building it from scratch. Whether that warrants a new term or just better documentation of ReAct-with-infrastructure is the argument the field is currently having.