"Loop Engineering" became a named discipline this week

cobusgreyling/loop-engineering hit about 6,400 stars in 27 days. That's roughly 237 stars a day, one of the highest velocities among genuinely new repos right now. Source.

The repo packages patterns, starters, and CLI tools for orchestrating coding agents in tight prompt/execute/review loops. What makes it a story instead of a repo is that the term is escaping its own README. "Loop engineering" is showing up as a topic tag on bigger projects (LobeHub, context-mode, omux), and there's a small constellation of tools implementing the same idea from different angles. omux orchestrates Claude Code and Codex as parallel subagents over tmux panes, with auto-continue and execute-then-review cycles. Source. When a practice gets a name and a starter kit and a topic tag in the same month, it's crystallizing into a discipline.

Why I care: naming a thing is how it gets teachable. For two years the good AI-assisted developers had a bunch of private tricks. Reserve the frontier model for judgment. Push grunt work to cheap subagents. Never let one context window try to hold the whole task. Run an execute step, then a separate review step, then loop. Those were folklore. Now they're a repo with issues and PRs and a vocabulary, which means they'll standardize, and the gap between people who know the tricks and people who don't will close fast.

This is the grassroots half of a bigger pattern (the vendor half is the next story, and they're describing the same thing). What's interesting is which side got there first. The practitioners named it before the vendors shipped the buttons. That almost never happens in tooling. Usually the vendor ships a feature and the community names the workflow around it. Here the workflow existed, got a name, and now the vendors are racing to productize it.

What to do: go read the loop-engineering repo, then look at omux if you run more than one coding agent at once. Even if you don't adopt either, the vocabulary is worth stealing. Being able to say "this is a review-loop problem, not a prompt problem" changes how you debug an agent that's spinning. And if you're building agent tooling, the topic tag is a free market map. The repos clustering under it are telling you exactly what solo builders are trying to wire together by hand right now.