We keep talking about “agent loops.”
Observe → Think → Act → Reflect → Repeat.
The language is everywhere: papers, product demos, architecture diagrams. Clean, circular and easy to draw on a whiteboard.
But a loop is a closed system that tends toward equilibrium or oscillation. Information that isn’t deliberately carried forward gets lost or compressed into a thinner and thinner summary. After enough cycles, the agent is effectively starting over with a foggy memory of why it chose the path it’s on.
That’s not how durable intelligence compounds. What we’re actually building (or should be building) is a helix.
Each cycle still moves through observation, decision, and action. But the decisions and the data from that cycle are deliberately recorded. They don’t disappear into a context window that will later be truncated. They become structured information that the next cycle can consult, query, and build upon. The trajectory is no longer circular. It advances along an axis of accumulating knowledge.
A loop forgets. A helix remembers why. And this difference is not semantic. It changes the architecture.
In a pure loop, the state that survives is usually a summary, a plan update, or whatever fits inside the current context budget. Intermediate reasoning, discarded branches, partial observations, and the exact justification for a choice three steps ago are treated as disposable. The system is forced to re-derive what it already knew.
In a helical design, the full decision-and-data history is treated as first-class material. It can be indexed, retrieved, summarized at multiple levels of abstraction, and still remain available in its original form when needed. The agent doesn’t just “remember” outcomes; it can inspect the reasoning that produced them.
The practical consequences show up most clearly on long-horizon tasks:
- A looping agent can lose the thread of why a particular approach was chosen after enough cycles.
- A helical agent can still surface the original decision trace, the data that justified it, and the outcomes that followed—then use that substrate for the next decision.
This also reframes how we think about memory and reflection. Instead of episodic retrieval bolted onto a looping core, the entire history becomes a continuously growing, traversable structure. The agent can move forward (what should come next) and backward (why are we here) with higher fidelity.
We’re still early. Most production “agents” today are loops with better tooling and longer context windows. The helical version requires deliberate investment in persistent decision logs, multi-resolution memory, and interfaces that let the model treat its own history as queryable information rather than disposable intermediate tokens.
But the distinction is worth making precise. Because the systems that compound intelligence over dozens or hundreds of cycles won’t be the ones that simply go around again. They’ll be the ones that carry the weight of every previous turn forward.
Top comments (0)