Why the Next Breakthrough in AI Will Come From Better Loops, Not Bigger Models

Kunal Grover

Hatched by Kunal Grover

Jul 21, 2026

9 min read

88%

0

The strange new bottleneck in AI is not intelligence, it is iteration

The most provocative thing happening in AI right now is not that models are getting smarter. It is that they are being wrapped in systems that make them useful repeatedly. A model that can answer one hard question is impressive. A model that can plan, inspect, revise, test, and continue working across an entire session is something else entirely. That shift changes the center of gravity from raw generation to operational cognition.

This matters because the biggest leap in capability may no longer come from a single forward pass. It may come from a loop: observe, act, evaluate, improve. In that sense, the real competition is not between models, but between workflows that can turn intelligence into durable progress. The most interesting recent developments all point in the same direction. One system manages multiple agents and long running tasks. Another can ingest images and videos so a coding agent can repair a UI from a screenshot. Another creates better training data by using agents to generate, judge, and regenerate examples until they actually discriminate between weak and strong solvers.

The deeper question is this: what happens when AI stops being a talker and becomes a worker that can improve its own work?


From prompts to production: the real unit of value is no longer the answer

For years, the basic mental model for AI was simple: ask a model a question, get a response. That made sense when the main product was text generation. But once models can write code, inspect interfaces, manipulate files, and coordinate with other agents, the value is no longer in a single answer. It is in the ability to complete a task with acceptable quality, under messy real world constraints.

That is a huge conceptual shift. A prompt is like asking a brilliant consultant one question. A workflow is like hiring a small team that can investigate, draft, critique, and ship. The consultant might give a beautiful answer. The team can deliver a finished artifact. And in practice, users do not pay for eloquence. They pay for outcomes.

This is why multimodality matters so much. A screenshot is not just an image. It is evidence. It is a bug report encoded in the language of reality. When an agent can ingest that screenshot, read the visual state of the product, compare it to an expected state, and then modify the codebase accordingly, the system moves from abstraction to execution. Likewise, video input means the agent can observe dynamics, not just static states. Suddenly, AI is not merely interpreting symbols. It is working with the substrate of work itself.

The same logic applies to long context windows. Large context is often described as more memory, but the deeper function is continuity. Continuity lets an agent carry the whole arc of a project, not just the last prompt. That changes the shape of the interaction from a sequence of isolated asks into a sustained collaboration.

The breakthrough is not that the model knows more. It is that the model can stay inside the problem long enough to matter.


Why the best data is no longer collected, it is discovered

There is another layer to this shift that is easy to miss. If agents are becoming workers, then data generation itself becomes a kind of work. That sounds obvious until you notice the implication: training data is no longer just a static asset, it is an active byproduct of intelligent process design.

Traditional self instruction pipelines often rely on cheap synthetic examples. But cheap examples tend to be shallow examples. They may look plausible, yet fail to separate the merely competent from the truly strong. That is the core weakness of many automated datasets. They produce volume without discrimination. They flood the system with training examples that are easy to answer and hard to learn from.

A more powerful idea is to treat data creation like adversarial craftsmanship. One agent generates candidate problems. Another agent, or a weaker solver, attempts them. A stronger solver attempts them too. A judge evaluates the gap. The orchestrator studies the failures and asks for regeneration from new angles. In other words, the system does not just make data. It hunts for informative friction.

That is a subtle but profound change. The goal is no longer to ask, “How much data can we create?” The goal becomes, “How much useful difficulty can we surface?” The best dataset is not the one with the most examples. It is the one that exposes the model to the border between what it can do and what it cannot yet do.

This is why agentic data generation is so exciting. It reframes evaluation and training as one continuous loop. The same mechanism that produces examples also identifies their weaknesses and repairs them. The data pipeline becomes self critical. And once that happens, compute becomes a quality filter, not merely a scaling factor.

Think of it like training a chess player. You do not improve by reading random games forever. You improve by finding positions that reveal your blind spots, then revisiting them until the pattern becomes instinct. The best synthetic data systems are doing the same thing at industrial scale.


The real race is for systems that can criticize themselves

If there is a single idea connecting these developments, it is this: agency matters more when it is coupled with evaluation.

An agent that can act but cannot inspect itself is just automation. An agent that can inspect but not act is just analysis. The powerful systems emerging now combine both. They can gather information, write code, test changes, read outputs, revise plans, and continue until the task is done. They can even optimize the process by which they are instructed, which means they are not only solving tasks, they are improving the machinery that solves tasks.

That creates an important new standard for AI systems. The question is no longer, “Can it generate?” The question becomes, “Can it close the loop?”

Closing the loop means four things:

  1. Perception: the system can see the relevant state, whether that is text, code, screenshots, logs, audio, or video.
  2. Action: it can change that state, such as editing files, calling tools, or producing artifacts.
  3. Evaluation: it can determine whether the change improved or worsened the outcome.
  4. Revision: it can adapt future behavior based on that feedback.

This loop is the real engine of progress. It is also why the most interesting frontier is not a single model benchmark, but the surrounding machinery: orchestration, critique, long context, tool use, and memory. A model alone is a mind. A model inside a loop is a system.

That distinction explains why some tasks remain hard even for very capable models. If a benchmark depends on the right abstraction, the right evidence, and the right feedback structure, then mere token prediction is insufficient. The system needs enough structure to ground its reasoning in the world. In other words, intelligence becomes practical only when it is embedded in an environment that can push back.


A useful mental model: AI is moving from language engines to labor systems

A helpful way to make sense of all this is to distinguish between three stages of AI maturity.

1. Language engine

The model responds to prompts. Value comes from its raw generative capacity.

2. Tool using assistant

The model uses code, search, images, and other inputs to complete tasks. Value comes from task completion.

3. Labor system

Multiple agents coordinate, critique, and improve each other over time. Value comes from sustained output quality and self improving workflows.

This third stage is where the most interesting transformation is happening. A labor system does not just answer requests. It manufactures throughput. It can do the equivalent of reading thousands of papers, generating candidate questions, filtering low quality items, and refining the whole pipeline based on validation results. It can also help a developer diagnose a bug from a screenshot, fix the code, and keep track of the larger project context.

The economic implication is enormous. If the old bottleneck was model intelligence, the new bottleneck is the design of work. Which tasks can be decomposed? Which signals are measurable? Which outputs can be judged automatically? Which forms of context can be captured in multimodal form? The companies that answer these questions well will not just have smarter AI. They will have better machines for producing outcomes.

This also suggests why valuation in the AI space keeps clustering around teams that can integrate models, infrastructure, data, and product into a closed system. The moat is increasingly not the model in isolation. It is the ability to orchestrate a system that learns from its own outputs.

In the future, the most valuable AI will not be the one that sounds the smartest. It will be the one that gets better at doing the work we care about.


Key Takeaways

  • Stop measuring AI only by answer quality. Ask whether it can complete a task across multiple steps, with inspection and revision.
  • Treat data as a discovery process. The best training examples are often the ones that expose genuine failure modes, not the ones that are easiest to generate.
  • Build loops, not demos. A useful AI system should perceive, act, evaluate, and revise. If one of those steps is missing, the system is fragile.
  • Use multimodal inputs as operational evidence. Screenshots, video, logs, and audio are not extra features. They are often the shortest path from confusion to action.
  • Optimize for criticism inside the system. Agents that can judge and improve their own outputs are far more scalable than agents that simply produce more text.

The hidden future of AI is not a bigger mind, but a better metabolism

We usually talk about intelligence as if it were a thing inside the model. But the more revealing analogy is metabolic. Intelligence in practice is the rate at which a system can take in information, transform it, test itself against reality, and produce useful change. A model that can only respond is like an organism with a mouth but no limbs. A model that can operate in loops is an organism that can eat, move, adapt, and survive.

That is the real transformation underway. AI is becoming less like a chatbot and more like an environment of collaborating workers that can gather evidence, propose actions, and improve through contact with consequences. The next leap will not come from asking one model to think harder in isolation. It will come from designing systems that make thought cumulative.

So the key question is no longer whether AI can speak fluently. It is whether AI can build, verify, and refine in the same motion. Once it can, intelligence stops being a performance and becomes a process.

And that changes everything.

Sources

← Back to Library

Hatch New Ideas with Glasp AI 🐣

Glasp AI allows you to hatch new ideas based on your curated content. Let's curate and create with Glasp AI :)

Start Hatching 🐣