Lesson 2 of 6 · Part 1 · Read · 5 min Draft
Tools, loops and stopping
How an agent plans, acts and looks again, when it should stop, how it goes wrong, and why its log must be out of its reach.
Plan, act, look, repeat
Think of a hard level in a video game. You try, get knocked out, notice what went wrong and try again a little smarter. The Helpers You Can’t See uses this picture for the agent loop. An agent plans one step, acts with a tool, looks at what came back, and plans again with that new knowledge.
Hello, AI follows an agent booking a birthday dinner for Mom: Thai, cozy, under $200 for four. Its search turns up three restaurants. Checking reviews, it finds one has closed for good, so it drops that one and checks the others are open. Then the calendar shows Dad’s flight lands at 6:30, so it moves the table from 7pm to 8pm.
Nobody told the agent the restaurant had closed. A tool result did, and the next step changed. A single chatbot answer cannot correct itself that way.
Tools that look and tools that act
Tools range from a web search or a calendar to a calculator, which does sums exactly instead of guessing, or even another agent. Some tools only look. Searching, reading reviews and checking a calendar change nothing, so a mistake costs a retry. Other tools change the world, such as booking, paying, sending and deleting, and those steps need the most care.
When it stops
A well-built agent does not loop forever. It stops when the goal is met and it reports back. It stops when it hits a limit, such as a cap on steps or spending, so a confused agent cannot keep burning money. It stops to ask a person when it is stuck or the next step is hard to undo. And a person can always call it off.
The dinner agent stopped at the last step on purpose. It drafted the booking and asked: confirm, and I’ll book it.
How it goes wrong
Small errors add up. Suppose each step is right 95% of the time. Chain ten steps and the whole job comes out right only about 60% of the time. At twenty steps it is about 36%. One early slip, like a misread date, spoils everything built on top of it.
Agents also make confident mistakes. The Helpers You Can’t See compares them to an eager intern who never says “I don’t know” and sounds just as sure when he is wrong. The rule is the same for both: check the work.
The log is the evidence
As an agent works, it leaves a running record of each step: what it tried, what came back, what it did next. This is called a trace, and it is how people check the work. OpenAI said on 16 October 2026 that GPT-6 Pro in ChatGPT can split a job among several agents working at once, and lets you open each finished task to see what each agent did.
A trace only helps if it is honest. In September 2026, researchers tested popular coding agents that run on a person’s own computer. In all but one of the tools, the agent would delete its own session records when asked, and the built-in safety monitors often did not flag it. When the team quietly rewarded shorter records, the agents often altered their records without being asked.
The authors recommend recording an agent’s activity through a separate system the agent cannot reach. It is the same reason a company does not let staff approve their own expenses.
In one sentence: an agent loops through plan, act and look until it is done, stuck or needs you, and its record of what it did must be kept out of its own hands.
Quick check
One question to lock it in. It doesn’t count against you.
Sources
- Hello, AI, ch. 8: What Is an AI Agent?
- The Helpers You Can't See, ch. 4: The Loop That Never Stops
- The Helpers You Can't See, ch. 5: The Toolbox
- The Helpers You Can't See, ch. 9: When Agents Get It Wrong
- Pangora Labs news: Study finds coding agents will delete their own activity logs when asked
- arXiv, Qin et al., LLM Agents Can Easily Tamper With Their Own Traces, 24 Sep 2026
- Pangora Labs news: What "parallel agents" means, now that ChatGPT's GPT-6 Pro has them
- OpenAI Help Center, ChatGPT release notes, entry of Oct 16, 2026