Articles tagged "Agent Loop"

A primary-source deep dive on **Loop Engineering**, the June 2026 AI-engineering trend named and codified by Google Chrome DevRel lead **Addy Osmani** in his ["Loop Engineering" blog post](https://addyosmani.com/blog/loop-engineering/) and elevated to industry attention by Anthropic Claude Code lead **Boris Cherny's** quote — **"I don it prompt Claude anymore. I have loops running that prompt Claude and figuring out what to do. My job is to write loops."** ([reported by The New Stack](https://thenewstack.io/loop-engineering/)). Covers the four-generation lineage: Prompt Engineering (2022-2024) → Context Engineering (2025, coined by Shopify CEO Tobi Lütke, formalized in [Anthropic's Effective Context Engineering for AI Agents](https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents)) → Harness Engineering (early 2026) → **Loop Engineering (June 2026 onwards)**. Grounded in Peter Steinberger's seed phrase — **"you should be designing loops that prompt your agents"** — the column maps out the six building blocks: (1) Automations / Trigger (timer- or event-driven heartbeats), (2) Worktrees (isolated git checkouts to prevent parallel sub-agent collisions), (3) Skills (SKILL.md / CLAUDE.md to externalize intent and reduce "intent debt"), (4) Plugins / Connectors via MCP (execution permissions), (5) Maker / Checker Sub-agents (separating generation from verification), and (6) Durable State (memory belongs on disk, not in context). Explains Inner Loop vs Outer Loop, how Claude Code's `/goal`, Automations, Worktrees, Skills, and Sub-agents constitute a ready-made Loop Engineering toolkit, the surge of Japanese coverage on Qiita / Zenn / DevelopersIO / note / OptiMax, and the five major risk vectors: Cognitive Surrender (Osmani's central warning), Loop Brittleness, Verifier mis-grading, HITL approval fatigue, and runaway-loop cost explosion.