The Loop Is the Harness: Design the better loop, the System Is Just Beginning
This week marks a quiet but complete paradigm shift: the center of gravity in agent development has moved from 'writing a good prompt' to 'designing a good loop.' That while-loop is no longer a plumbing detail—it determines whether a system converges, how it brakes, and whether costs spiral out of control. Models are being commoditized fast, and the harness—the system that assembles models, tools, context, feedback, and constraints into a loop—is what separates the mediocre from the exceptional. Our 24 picks, from Boris Cherny's loop engineering manifesto and Claude Code's four official loop patterns, to context caching engineering, Skill design philosophy, and multi-model collaboration at the serving layer, form a construction manual for this new mindset. After this issue, you'll stop asking which model is better—you'll ask: can my loop survive a night, stay within budget, and deliver usable results?
The Loop Designer: When Coding Becomes Designing Closed Circuits
This week's edition is dominated by a single, powerful theme: the shift from one-shot prompting to autonomous loops in AI-assisted coding. The community produced a complete spectrum of content around Loop Engineering—from conceptual frameworks and technical breakdowns to real-world case studies. The clear signal is that the most effective AI workflows aren't about crafting a perfect prompt, but about designing closed-loop systems that discover, execute, verify, and iterate on their own. Alongside this main thread, we've curated deep dives into design specs, resource budgeting, and code review—all addressing a common question: when AI becomes abundant, what becomes the scarce human skill? By the end of this issue, you'll see that prompt writing is just the beginning—designing loops is the real threshold under the new normal.
From Foxconn to Software Factory: The Paradigm Shift in Agent Architecture
This week's picks converge on a single, defining tension: while AI models are growing exponentially smarter, our system architectures often remain stuck in the old era of 'wrapping untrustworthy models in mountains of code.' Garry Tan's series of essays lands like a bomb, articulating a new paradigm of 'thin harness, fat skills' backed by 810x developer output and a self-improving skill system. Meanwhile, Anthropic's 400K-session analysis, CREAO's cloud sandbox lessons, and the engineering practices of Hermes Agent and Factory 2.0 all corroborate the same trend: we've been building isolated 'Foxconn factories' for each agent, but what we need are composable, self-evolving 'software factories' that span platforms. This issue is about the paradigm shift happening right now—from questioning naked models to building systems, from heavy frameworks to lean skills, from monolithic agents to pluggable ecosystems.
The Compounding Agent: From Prompt Engineering to Self-Improving Systems
This week’s picks converge on a clear inflection point: AI agents are graduating from conversational fluency to engineering maturity. The bar is no longer the quality of a single response, but whether an agent can self-correct across hours, accumulate memory across sessions, and let humans operate as architects rather than operators. The editorial arc moves from a leap in model capability—Anthropic's Fable 5—to the cognitive bottleneck that emerges when scaling agent use (the orchestration tax), and finally to the engineering practices that deliver compounding returns: rigorous AGENTS.md files, dynamic workflows, and cross-session memory loops. A recurring law emerges: real leverage comes not from spawning more agents, but from designing systems where each run’s failures, lessons, and rules form the training data for the next. This is the pivot from prompt-driven to design-driven agentic engineering.
When Agents Keep Their Own Schedules: From Babysitting to Set-and-Forget
AI coding crossed a critical threshold this week. The ‘agent’ in our headlines gained a tense—it learned to sustain itself, orchestrate its own resources, and deliver finished work. From Anthropic’s dynamic workflows that let Claude write its own harnesses, to Cursor’s revelation that 35% of their merged PRs now come from cloud agents, the paradigm is shifting from single-prompt transactions to multi-hour autonomous deliveries. The developer’s role is being recast as a dispatcher and reviewer. This new power demands new disciplines: you’re no longer just writing code, but designing contexts, curating memory, and understanding token economics as a first-class system constraint. This issue of Glean traces the emerging blueprint for managing autonomous agents—covering the orchestration patterns, memory architectures, and counterintuitive engineering lessons that separate functional systems from token-burning chaos.
From Prompts to Harnesses: The Next Leap in AI Engineering
This issue of Glean captures a pivotal moment: AI engineering is shifting from crafting clever prompts to building enduring harnesses that let systems self-improve and ship. From Anthropic’s roundtable to production stories at Creao and Cloudflare, the message is clear—the environment around the model now matters more than the model itself. Deep-dive guides on taming Claude, battle-tested patterns for agentic workflows, and the latest in data infrastructure all point toward a new engineering discipline. Whether you’re a frontline developer, tech lead, or architect, this collection will help you close the gap between ad-hoc AI use and disciplined system building.
Mondays · one email
Each week’s picks, gathered into one issue and sent to your inbox. Just your email — no ads.