---
title: "Loop Engineering"
url: https://daily.dev/posts/loop-engineering-og7g7dfqd
source_url: https://addyosmani.com/blog/loop-engineering
type: article
source: "Addy Osmani"
author: "Addy Osmani"
published: 2026-06-08T00:32:43.190Z
updated: 2026-06-10T17:00:12.294Z
tags: ["ai-agents", "claude-code", "codex"]
reading_time: 12
upvotes: 3
comments: 1
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Loop Engineering

**[Addy Osmani](https://daily.dev/sources/addy)** · [@addyosmani](https://daily.dev/addyosmani) · 12 min read · 3 upvotes · 1 comments

## Summary

Loop engineering is the practice of designing automated systems that prompt coding agents on your behalf, rather than manually prompting them yourself. Built on five primitives — automations (scheduled discovery/triage), worktrees (parallel isolation), skills (reusable project context), plugins/connectors (MCP-based tool integrations), and sub-agents (maker/checker separation) — plus persistent external state, these loops now ship natively in both Claude Code and Codex. A concrete example shows a morning automation that reads CI failures, spawns isolated worktrees per finding, drafts fixes with one sub-agent, reviews with another, then opens PRs and updates tickets automatically. The author warns that loops amplify both productivity and risk: verification responsibility remains with the engineer, comprehension debt grows faster when you don't read what the loop produces, and 'cognitive surrender' — letting the loop think for you — is the real danger. The leverage point has moved from writing prompts to designing the system that writes them.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://addyosmani.com/blog/loop-engineering>

## Community discussion

Top comments from developers on daily.dev.

**@idoshamun** · 0 upvotes

> If you don't build frontends, your life is easier with those agents. Less verification to do especially with high trust test suite. Once you do frontend, you must manually verify everything (for now). Putting aside all the tokens these loops require. Peter spends millions a month in tokens. It's hard to use him as reference

## Similar posts on daily.dev

- [Loop Engineering](https://daily.dev/posts/loop-engineering-h663rbtdz) · Elevate · 3 upvotes · 0 comments
- [An Introduction to Loop Engineering](https://daily.dev/posts/an-introduction-to-loop-engineering-7ctzwxfxz) · Machine Learning Mastery · 2 upvotes · 0 comments
- [Loop Engineering, Clearly Explained\!](https://daily.dev/posts/loop-engineering-clearly-explained--mt3qmkm25) · Daily Dose of Data Science \| Avi Chawla \| Substack · 3 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#claude-code](https://daily.dev/tags/claude-code), [#codex](https://daily.dev/tags/codex)

[View this post on daily.dev](https://daily.dev/posts/loop-engineering-og7g7dfqd)