File size: 2,609 Bytes
9ec4919 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 | # Sourced Signals And Quotes
This page records short sourced signals around the emerging Loop Engineering concept. It is not a substitute for the original sources. Use it to understand provenance, then read the linked material directly.
## Addy Osmani
Source: [Loop Engineering](https://addyosmani.com/blog/loop-engineering/)
> "Loop engineering is replacing yourself as the person who prompts the agent. You design the system that does it instead."
Why it matters: This is a direct definition of the shift from manual prompting to designing the recurring system that prompts, checks, and continues.
The same article states:
> "Loop engineering sits one floor above the harness."
Why it matters: This anchors the repository's four-layer framing: prompt, context, and harness engineering improve agent runs; Loop Engineering governs repeated agent work over time.
## Peter Steinberger
Source: Addy Osmani's [Loop Engineering](https://addyosmani.com/blog/loop-engineering/) article reports this statement from Peter Steinberger.
> "You shouldn’t be prompting coding agents anymore. You should be designing loops that prompt your agents."
Why it matters: This is one of the clearest formulations of the human role moving from turn-by-turn prompting to loop design.
## Boris Cherny
Source: [I Now Just Write Loops To Prompt Claude Code: Claude Code Creator Boris Cherny](https://officechai.com/ai/i-now-just-write-loops-to-prompt-claude-code-claude-code-creator-boris-cherny/)
> "Now it’s actually leveled up, I think, again, to the next wave of abstraction where I don’t prompt Claude anymore. I have loops that are running. They’re the ones that are prompting Claude and figuring out what to do. My job is to write loops."
Why it matters: This is the practical workflow claim behind the concept: the developer designs the system that prompts, evaluates, and decides what to do next.
## Anthropic
Source: [Building effective agents](https://www.anthropic.com/engineering/building-effective-agents)
> "Consistently, the most successful implementations use simple, composable patterns rather than complex frameworks."
Why it matters: Loop Engineering should stay contract-driven and composable. The goal is not to add complexity for its own sake.
The same article also states:
> "When building applications with LLMs, we recommend finding the simplest solution possible, and only increasing complexity when needed."
Why it matters: This supports a conservative maturity path: start with explicit state and verification before adding multi-agent orchestration or production autonomy.
|