
The Agent Is a Loop, Not a Person
An agent is not a colleague. It is a loop with tools, memory, and a stopping rule. Treat it like a person and you will design the wrong system.
Read the essayIssue 14 · August 2026
Julian Hale writes from Portland about autonomous loops, the tools they touch, and the quieter craft of building systems that hold together on a Tuesday.
This month on agents

An agent is not a colleague. It is a loop with tools, memory, and a stopping rule. Treat it like a person and you will design the wrong system.
Read the essayFeatured series

The model is not the product. The tools are. Most “agent intelligence” is a well-named function with a strict schema and a boring implementation.
12 min read

Add a second agent and you have not added a colleague. You have added a coordination problem, a shared lie about memory, and twice the ways to stop too late.
13 min read

The goal is not an agent that remembers everything. The goal is an agent that remembers the few facts that should change next week’s work.
11 min read

If you cannot say what better looks like on Tuesday morning, you do not have an agent product. You have a demo with a marketing site.
12 min read

Some work wants a button, a form, or a person. Agents are expensive loops. Use them when the path is unknown and the checks are strong.
10 min read

A cheap review trick: read the change out loud as if you were explaining it to a skeptical friend who cannot see the screen.

Every layer you add is a place for a junior engineer to get lost and a senior engineer to hide. Charge rent for both.

Boring software is not a lack of taste. It is taste applied to other people’s Tuesdays.

Finished is a feeling. Shipped is a date. The work is learning how to make the unfinished part obvious and safe.

A good interface does not only accept input. It teaches the shape of the system while your hand is still on it.

A week of meetings can look like a week of work. It is often a week of avoiding the one page that would have moved the project.

When a system will not yield, I stop typing code and start typing sentences. The bug is often a story we have not finished.

For two years we read one paper or essay a week, out loud, with a hard stop. It changed how the team argued more than any offsite.

A site that cannot lie about its backend is a good place to practice product honesty. The files are the system.

The author
Julian Hale writes about autonomous agents and the quieter work of making software. He spent a decade on developer tools, then three years on agent systems at a lab that no longer uses that name. He lives in Portland, Oregon.
More about JulianThe letter
New essays, a reading or two, and no weekly guilt. This form is fake, like the rest of the machinery here.