Tutti parlano di Loop Engineering... ma nessuno te lo spiega così
The video traces the evolution of AI interaction paradigms from Prompt Engineering through Context Engineering, Harness Engineering, to the newest Loop Engineering approach. Loop Engineering involves wrapping autonomous AI workflows in iterative loops that self-improve toward defined goals without requiring manual intervention between steps.
Summary
The transcript discusses the evolution of AI engineering methodologies over time. Prompt Engineering was the initial approach where developers wrote detailed system prompts to instruct AI models on their role and behavior, with performance depending on prompt quality. Context Engineering emerged as models gained access to tools and could read files, search the web, and call APIs through protocols like MCP, but faced the problem of context rot—performance degradation when token counts exceeded 200,000. Harness Engineering solved this by structuring tasks into subtasks, using persistent file-based memory (markdown files) to maintain state between sessions, and reinitializing the agent at each step rather than compacting context. Loop Engineering, promoted by Boris Cerni (Cloud Code) and Peter Steinberger (Open Claude), represents the next evolution by placing entire Harness Engineering workflows inside iterative loops that run autonomously based on triggers and verification conditions. The system cycles through execution and verification phases, writing results to memory files and triggering new loops based on events (GitHub issues, emails) or scheduled times. Key to Loop Engineering's success is defining measurable goals with termination conditions to prevent infinite loops. The speaker presents five verification levels: deterministic (boolean pass/fail), rule-based (numerical constraints), delayed truth (results verified later), LLM-as-judge (model self-evaluates), and human checkpoint (human review). The practical benefit is developers no longer manually prompt "improve this, improve that" but instead set a goal and let the loop run autonomously. The video concludes with a real example of Loop Engineering optimizing matrix multiplication code, achieving 320x speedup over 10 automated iterations without manual intervention.
Key Insights
- Boris Cerni and Peter Steinberger shifted their approach from writing prompts directly to designing loops that automatically generate prompts, fundamentally changing how developers interact with AI agents
- Context rot degrades AI model performance drastically above 200,000 tokens due to increased confusion from excessive input, requiring external management strategies
- Harness Engineering uses file-based persistence (markdown files) as an external memory system to avoid context compaction penalties, allowing agents to maintain state across sessions
- Loop Engineering creates nested loops—tool-calling loops within Harness loops within outer iteration loops—enabling autonomous cycles that eliminate the need for repeated manual prompting
- Five verification levels exist for loop goals: deterministic boolean conditions, numerical rule constraints, delayed truth outcomes, LLM self-evaluation, and human checkpoints, each suited to different problem types
Topics
Transcript
[0:00] And here we are once again with a new term that is going super viral called loop Engineering. Everyone is really talking about it. We went from prompt Engineering to Context Engineering to Arnest Engineering which lasted very little and now we have already entered this new era of Open Engineering. What is it? Is it all hype? Is it marketing? we'll find out in this video. This new, let's say, paradigm was [0:31] launched by these two characters here in the Tech world and I who are super famous. Let's talk about Boris Cerni, the creator of Cloud Code, who in a recent interview said these words where he says that he no longer writes the prompts on…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Simone Rizzo
Gemini 4 Argon é stato appena annunciato da Google e rappresenta a detta loro il nuovo modello AI
Google announces Gemini 4 Argon, a new AI model claimed to compete with OpenAI and Anthropic offerings, featuring strong performance across benchmarks and enhanced security against prompt injection attacks. The model will be released through a staged rollout starting with the Fairwind Program for selected companies, followed by API access for developers, and eventually public release.
OpenAI dots compete con grokbot il nuovo gpt 6.1 sol compete con opus 5.5 tutto questo è successo
OpenAI released multiple new frontier models including GPT 6.1 Sol at significantly lower token costs, along with cloud-based agents called Dots that compete with Grockbot. The company introduced new subscription tiers, collaborative spaces, a Decisions API for real-time decision-making, and cloud-based coding tools, while Elon Musk strategically acquired dots.com to redirect traffic to Grockbot.
OpenAI copia Grok con i dots? GPT-6.1 sfida Opus 5.5
A comprehensive analysis of OpenAI's DevDay announcements, including new AI agents called 'Dots,' the GPT-6.1 model, and pricing changes, alongside broader trends in AI development from competitors like Anthropic and open-source projects. The speaker critiques the announcements as largely incremental improvements rather than groundbreaking innovations.
Apple rilascia un nuovo modello AI si chiama LensVLM e cerca di risolvere il problema dei token in
Apple releases LensVLM, a fine-tuned 9 billion parameter model based on Qwen 3.5, implementing a novel technique called Selective Context Expansion that converts text into images to achieve 15x token compression. This approach allows visual language models to handle large text inputs more efficiently while maintaining reasoning accuracy.
Usare Jev per risparmiare tantissimi token nel tuo agente AI mantenendo alte le prestazioni.
Tamara discovered a method to use JEV, a fast decision-making model, to replace the slow slash compact function in AI agents. By having JEV decide whether to keep or discard function outputs, the system clears context window space much faster while maintaining performance. The solution, called Fast Jeev Comp, has gained significant popularity and can also be run locally using open-source models.