In June 2026, Boris Cherny, the creator of Claude Code at Anthropic, told The New Stack he had stopped prompting Claude directly: he writes loops instead. They prompt Claude, decide what to do, and chain steps together. Addy Osmani (Google Chrome) named this practice loop engineering, and the term immediately caught on in dev circles.

Good timing. Because the practice itself already existed.

The Genealogy of the Prompt

Before talking about loops, you have to talk about prompts. Where do they come from?

Chat interfaces imposed a specific model: type an instruction, wait for a response, type again. Developers naturally started saving their repetitive instructions: system prompts, expected output formats, recurring constraints. That was already a manual loop. "Type this, then that, then that." The chat interface just limited what you could do beyond it.

A prompt was never an atomic unit of AI. It was a unit of interface. An instruction in a chat form.

n8n Already Had Loops

Tools like n8n have had loops for years: trigger, nodes, recurring output. What was missing was agentic nodes. They added them.

The structure stays the same. What changes is the nature of certain nodes: non-deterministic, they decide which branch to take based on context. This is not an architectural revolution. It is an evolution in the nature of nodes.

Loop engineering does not invent a new topology. It equips an existing topology with nodes capable of reasoning.

Claude Code Democratizes the Mechanic

What Claude Code changes is accessibility. You can now create a loop without configuring n8n, without drawing a workflow, without connectors between tools. The principle stays the same: scripted or LLM steps, recurring trigger, automated output. The barrier disappears.

That is a real gain. A solo developer can today orchestrate multiple agents in parallel across multiple projects without dedicated infrastructure. What used to require an entire DevOps stack fits in a few files.

KittyClaw Was Not Born from a Loop Vision

KittyClaw was not born from a theoretical reflection on loop engineering. It was born from a concrete need: capture ideas without losing them, prioritize, delegate (writing, tests, fact-checking, images, merge conflicts), and know instantly, by looking at the Kanban, what is progressing, what is blocked, what made it to production.

Not a vision. A need.

And that is where most current discourse on loop engineering misses something essential.

The Cockpit Is the Missing Piece

The current debate focuses on automating prompts. What it forgets is the other half of the problem: an autonomous loop without a human feedback interface is a black box.

Without feedback, you do not know what made it to production. You do not know what is waiting to be unblocked. You do not know what should not have been done. It is the equivalent of telling an employee to run the shop without ever giving them any feedback, without ever looking at what they produce.

Loop engineering solves the upstream problem: automate execution. It does not solve the downstream problem: understand what happened and decide what comes next.

KittyClaw is exactly that missing piece. The cockpit for the loop.

Two Levels of Feedback

The distinction matters, because there is not just one type of feedback.

Operational feedback: the Kanban. Tick by tick. In real time. Did the agent make progress? Is it blocked? What is it waiting for? The Kanban answers these questions without reading logs. That is execution feedback, happening now.

Strategic feedback: the Dashboard. Metrics, KPIs, editorial calendar. Is the publication cadence holding? Are tickets piling up? Is a project stagnating? The Dashboard answers these questions for fundamental decisions, not for tick-by-tick tracking.

Both together genuinely close the loop. Without one, you lose the thread mid-execution. Without the other, you lose direction entirely.

What Loop Engineering Is, and What It Is Not

Loop engineering is a real engineering discipline. Designing a loop is serious work: defining agents, triggers, stop conditions, blocking cases, transitions. It is not configuring a chatbot. It is designing an autonomous system that will make decisions.

But autonomy is not an end in itself. A loop without a cockpit is not a mature loop. It is a blind loop.

Closing the feedback loop is what transforms an automation experiment into a production system. And that is exactly what current discourse forgets.