Observed Signal · Jun 22, 2026 · Conference Presentation · Source: techcrunch · Impact: 3/5 · Sentiment: Positive
AI Agent Loops Mark Next Big Step
At Meta’s @Scale conference, Claude Code creator Boris Cherny argued that "loops" — continuous agentic workflows where agents prompt and supervise other agents — are a real and significant advance in AI. Cherny described persistent loops used to continually improve code architecture and unify duplicated abstractions, with subagents submitting pull requests and running indefinitely. The article situates loops alongside recursive programming concepts and cites techniques like the Ralph Loop to avoid agent drift. It also notes trade-offs: loops increase test-time compute and token consumption, raising costs for many businesses even as they enable ongoing, automated improvements. The piece highlights both the technical promise of agentic loops and operational challenges such as oversight, token budgets, and runaway spend.
Agentic loops represent a notable technical evolution for persistent AI-driven workflows that could change how software and operations are automated, but they also introduce substantial compute/token cost and governance challenges that limit immediate broad adoption.
Track Meta Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Boris Cherny, creator of Claude Code, spoke about agentic "loops" at Meta’s @Scale conference and said they are "for real."
- Cherny described loops where agents continuously run in the background, e.g., agents that improve code architecture and unify duplicated abstractions and submit pull requests.
- The article links agentic loops to classical recursive loops and mentions the Ralph Loop technique for keeping models on-task.
- Noam Brown (OpenAI researcher) is cited for the view that throwing more compute at models can solve many problems, underpinning the rationale for continuous loops.
- Agentic loops substantially increase test-time compute and token usage, creating potentially high operational costs for organizations that do not sell tokens.
Connected Companies & Entities
4 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Loop Engineering: Automating AI Coding Agent Workflows
Loop engineering is the practice of designing automated systems that drive AI coding agents end-to-end instead of interacting with them manually. The article describes five core building blocks—automations (scheduled discovery/triage), worktrees (parallel agent isolation via git), skills (persistent project context), plugins/connectors (MCP-based tool integrations), and sub-agents (maker/checker separation)—and a sixth element, external memory (e.g., markdown files or a Linear board), that links runs across sessions. It explains how these pieces combine into self-running loops that triage CI failures, draft fixes, review changes, open pull requests, and update tickets autonomously. The author notes practical benefits and warns of costs and risks including token expense, comprehension debt (shipping code you don't understand), and cognitive surrender (loss of human engagement). The concept is attributed to engineers at Anthropic and OpenAI and appears in tools such as Claude Code and Codex.
Loop Engineering: Designing Agentic Loops Not Prompts
The newsletter explains the emergence of “loop engineering”: designing automated agent loops that repeatedly run until a goal is met rather than manually issuing prompts. The idea traces to Geoffrey Huntley’s “Ralph” loop and grew as models improved. Major agent harnesses added a /goal primitive (Codex, Hermes, Claude Code) that compresses Ralph-style loops into a single command and handles state, lifecycle, and budgets. Developers report common uses are trigger-based automations and scheduled (cron) jobs — e.g., auto-opening PRs for Sentry issues, stabilizing flaky tests, triaging outages, nightly e2e test babysitting, and migrations. Objections include agent drift, poorer results versus human-in-the-loop, and high token costs (”tokenmaxxing”). Some engineers view loops as a temporary workaround now baked into harnesses; others say deep loop engineering mainly matters for AI infrastructure builders.
AI Agents Are Feedback Loops — Introducing Loop Engineering
A developer-written essay argues that modern AI agents are not magical but operate as iterative feedback loops, and proposes 'Loop Engineering' as a discipline for designing reliable agent workflows. The article contrasts traditional prompt engineering with loop engineering, outlines three core loop pillars (actions, feedback, stop conditions), and uses a coding agent example to show how loops should include verification, tools, memory, and stopping rules. The author also mentions git-lrc, a free, source-available micro AI code reviewer that runs on every git commit and is hosted on GitHub.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.