loop-engineering vs loopy
Reference repo plus npm CLIs (loop-init/audit/cost) for loop engineering: designing scheduled, gated control loops that prompt and orchestrate AI coding agents — Grok, Claude Code, Codex — over time. — versus — A public library of reusable AI-agent loops plus Loopy, an installable skill that helps agents find, audit, adapt, run and publish loops from the live catalog.
Same conviction — the loop is the unit of agent work — expressed differently: loop-engineering teaches you to design gated control loops; Loopy catalogs finished loops so you can borrow instead of design.
| loop-engineering | loopy | |
|---|---|---|
| Stars | 8.0k | 2.7k |
| Forks | 1.1k | 235 |
| Language | JavaScript | JavaScript |
| License | MIT | MIT |
| Last activity | today | 9 days ago |
| Topics | coding, orchestration | skills |
| Curated connections | 7 | 2 |
loop-engineering — the curator's take
The methodology layer for autonomous coding agents — read it once you've stopped hand-prompting and want to design the loop that prompts the agent instead: scheduled triage, worktree isolation, maker/checker sub-agents, MCP connectors, human gates, and a phased L1-report → L3-unattended rollout. Ships 7 clone-and-run patterns, tool-agnostic starters (Grok/Claude Code/Codex/OpenCode), and CLIs that score loop-readiness (loop-audit), estimate token spend (loop-cost) and scaffold state/budget (loop-init). It's a patterns + tooling reference, NOT a runtime — it won't execute or host your agents, so bring your own harness (an alook-style AI-company layer or a squid-style pipeline). Overkill if you just want one-shot interactive help; heed its own caveat that unattended loops make unattended mistakes, so verification stays on you.
loopy — the curator's take
The insight: most agent work is a repeatable loop someone already designed — so catalog them. The website is browsable by humans AND agents (llms.txt, JSON catalog, agent guide), and the Loopy skill turns your agent into a loop librarian: discover, audit, repair, debrief, publish. Genuinely useful for not reinventing the same research/review/refactor loop weekly. NOT a runtime — loops are prompts and procedure, not executable infrastructure; quality varies by contributor, so audit before you adopt (the skill's audit step exists for a reason).