The agent body

Every agent product is built from the same short list of parts: a model, a prompt, a set of tools, a few skills, some memory. The parts are rented from a handful of providers, and every builder rents the same ones. Described by their parts, the products are indistinguishable, and most of the time they feel that way too. Yet some of them improve week over week and hold onto their users, while others with an identical parts list stay demos nobody opens twice. The parts cannot be the difference, because the parts are shared. Positioning is the usual explanation, and positioning is not it either. The difference is the body, and the body is the part almost nobody describes.

What a body is

Physically, a body is whatever persists when the model is not running. A model call is stateless. Each time the agent acts, its mind is assembled from scratch, the model and the prompt and the tools it is told about and the documents pulled in on its behalf, and when the call returns, that assembly is gone. Nothing the agent learned during the call survives inside the model, because the model is the same weights afterward that it was before and will be for the next call. So whatever the agent carries from one moment to the next has to live somewhere that outlasts the call. That somewhere is the body. A body is the place where an agent’s history, its learnings, and its standing can exist at all, because a mind that vanishes at the end of every call cannot carry anything.

Why a boundary

A place to keep things is necessary but not sufficient. A pile of records with no edge around it is not a body, because nothing about it says which records belong to this agent and which belong to the world. The missing part is a boundary, a line that marks this much as inside and the rest as beyond. The boundary is not a limit grudgingly accepted in exchange for safety. It is the part that does the work, and it works in three ways.

The first is that a boundary makes failure mean something. An agent that is for everything has no particular outcome that counts as failing, so no measurement can say whether this week’s version beats last week’s, and there is nothing specific to optimize against. A bounded agent has a defined job, and a defined job produces a defined error. This is the mechanical reason bounded products improve across versions while unbounded ones stay demos: only the bounded one throws off a signal it can climb.

The second is that a boundary is what a person can hold in mind. Someone delegates to a tool only when they carry a model of it, and the model they carry is mostly a boundary, this is what it is for and this is where its job ends and mine begins. An agent that offers to do anything asks its user to hold “anything” in mind, and attention slides off anything. Plenty of capable agents go unused for exactly this reason. The capability is real, but nobody can keep a shapeless capability in mind long enough to build a habit around it.

The third is that a boundary is what lets anything accumulate. Learnings, records, and standing pile up only because there is an inside for them to pile up in. With no edge, every record the agent produces is more undifferentiated world, indistinguishable from everything else that happened. The membrane is what turns a stream of events into the history of one particular thing.

Biology settled all of this early. A cell is not defined by its contents, which turn over constantly, but by the membrane that holds those contents together and controls what crosses in each direction. Remove the membrane and the cell does not become a bigger, freer cell. It disperses into the medium and dies, because death, in thermodynamic terms, is equilibrium with the surroundings: unlimited free exchange, nothing maintained. Theoretical biology gave this a name, autopoiesis, meaning that a living thing is the process that produces and maintains its own boundary.^[1] The free-energy principle in neuroscience makes the matching claim from the other side: a system persists exactly to the degree that it keeps its inside statistically different from its outside.^[2] An agent that can touch anything and be touched by anything is a cell without a membrane, in free exchange with everything and maintaining nothing.

This is also why bounded things specialize, and specialization is where power comes from. A liver is enormously capable inside its boundary and useless outside it, and the boundary is precisely what makes it improvable, because a defined job produces a defined error. An agent product obeys the same rule. The ones that get better are the ones that maintain a membrane.

Why unity

A boundary settles what is inside, and a body usually has several things inside it: a part that holds money, a part that holds correspondence, a part that holds the work queue. For these to be one body rather than a heap of parts, they have to present themselves to the world as a single continuing thing, with one name and one history. Unity is not a nicety here, it is what makes the accumulation worth anything. Standing attaches to an identity, so if the parts answer to no single name, there is no one for a counterparty to come to trust. A history is the history of something, so if the parts keep separate records, no single thread gets longer and more valuable with use. Learnings improve one improvable thing only when there is one thing for them to improve. The parts hold together as a unit by coordinating through shared state: an action taken in one part is written where the others read it, so what one part did becomes something all of them know. That shared record is how many organs behave as a single agent, and it is why the agent can answer for what it did last week, since the week is in the record and the record is the one the whole body shares.

Mind and body

With the boundary and the unity in place, the mind and the body separate cleanly. An agent, seen whole, has a mind and a body. The mind is the model plus everything assembled into its context for a single call: the prompt, the tools it is told about, the skills and instructions it is handed, the documents retrieved on its behalf. The mind is stateless and temporary, put together for one call and gone when the call returns. The body is everything that persists between calls, bounded by the membrane and unified under one name. A body answers five questions:

• How does the agent persist? What state, records, and accounts remain when no model is running?
• What organs does it have? Which functional parts own which piece of its domain?
• How do the organs coordinate? Through what shared state does one part find out what another did?
• What functions do the organs perform together? Which capabilities exist only in the composition, the way circulation exists in no single organ?
• How does the agent maintain unity? What makes its parts present themselves to the world as one continuing thing with one name and one history?

The parts

In practice the answers recur, so a body has a recognizable parts list. At the center is a durable record, and the relationship between agent and record runs opposite to intuition: the agent does not have a memory so much as the memory has an agent, one record that successive minds visit, read, and extend. Around it sit the organs, each owning one piece of the domain and coordinating through that record rather than through each other. There are inbound channels, an inbox and webhooks and triggers, through which events reach the body whether or not any model is running, because an agent that can only be prompted has half a body at most. There are its own addresses and accounts, the surfaces through which it acts and is known, because standing with other parties attaches to an address rather than to a model.

And there are constraints: spending limits, sending rules, approval gates in front of anything irreversible. The body is defined by these as much as by its capabilities. A wallet with no spending rule is an open channel through which one bad call becomes an unbounded loss, and the rule has to arrive with the wallet, because adding the constraint after the first incident means the first incident was the design process. Constraints are also how the boundary stays a boundary: a limit the body enforces on itself is the membrane doing its job from the inside. Finally, there are written rules the body can be reprogrammed with, which is where human review pays off, since a rule written down today is a part of every mind assembled tomorrow.

Four products

Real agent products sort cleanly under this frame.

A chat assistant has the largest mind and the thinnest body. The mind is a frontier model with conversation context and a few injected memories; the body is a conversation log and a user profile, with no addresses, no accounts, and no organs. The thin boundary explains both of the product’s famous properties. Everyone knows what a chat is for, so the product binds attention instantly, and almost nothing accumulates inside the membrane, so users defect the day a better model ships.

A coding agent has an ordinary mind (a model, a system prompt, file and shell tools) and a superb borrowed body: the repository, with its working tree, branches, tests, and continuous integration. The repository explains why coding agents worked before most other agents did. A repo is a ready-made membrane with a built-in error signal, because a failing test is exactly the bounded, optimizable failure that an unbounded agent never gets to have.

An autonomous business agent inverts the chat assistant. Its mind is swappable and unremarkable, and its body is the heaviest in the list: a payment account, an inbox, a domain, a ledger of records, and the credentials that hold them, with approval gates in front of spending and sending. The boundary is literally the credential set, since inside is whatever the body holds a key to. That is why this class can run unattended, because events arrive through its own channels, and why its progress survives a change of model, because everything accumulated lives on its side of the membrane.

An embedded product agent, the assistant that lives inside an existing application, has a purpose-built mind and no body of its own. It borrows the host’s: the host’s database, permissions, queues, and users. The borrowed boundary explains the whole trade. The agent is good on its first day, because it inherits a mature body, and it can never leave, because the body was never its own and the identity the world sees belongs to the host.

Three questions

Any product in this list, including one you are building, can be checked with three questions:

• Does the agent know what it did last week? A body holds its own history; a visiting mind holds nothing.
• Does an action taken through one surface show up everywhere? Every other place the agent lives should see it, because the organs coordinate through shared state.
• Does it defend its own invariants? Refusing, on its own, the action that would cross one of its limits.

Three yeses is a body. Fewer, and what exists is a mind making visits: capable, stateless, and gone when the call returns.

The minds are converging anyway. Every builder rents them from the same few providers at the same prices, and a better one is available to every competitor on the day it is available to you. The body is the part that cannot be rented, which is why the body is what a company actually makes. The direction this points is many such bodies existing digitally, each maintaining its own boundary and finding its own market.