How it works
A harness answers three plain questions for every agent. What wakes it? What does it get to read? Where does its output go?
The agents I work with wake in different ways. Some run on a schedule and check for tickets in the morning. Some react to an event: a ticket, a comment, a build. Some run in loops that look for useful work, and some work toward a goal for 24 or 36 hours.
The work then moves through stages that the harness fixes in advance. For example, the transcript of a meeting lands in a folder of a repository and a monitoring process notices it. An agent reads it with a skill written for that kind of file and extracts decisions and tasks. Those become tagged tickets. Other agents react to the tags: one updates documentation, another implements, another reviews the result.
None of those steps needs me at the keyboard. The laptop is only an interface.
Where it shows up in real work
My own agents already run for long periods without me, and I noticed that meetings were the place where I was still the integration layer. I would close a call, write notes, copy context, create a ticket and point an agent at the right repository.
So I am building what I call a physical agent harness: a small portable station with an iPad mini, an external camera, a microphone, a light, a USB-C hub and a battery. The conversation is transcribed, and an agent can work out which client and workspace it belongs to, which decisions were made and what must become a ticket. The meeting stops being text that I process later. It becomes an event that enters the same infrastructure as the rest of the work.
The physical harness captures what agents cannot normally see: human conversation, intent and decisions. The software harness handles what happens next.
What it is not
A harness is not the model, and it is not a single agent. It is also not a promise of full autonomy. Some checks stay hard to automate, such as judging whether an interface feels wrong, and the answer to those is usually one more layer in the harness, with a person who reviews the important output.
When you need one
You need a harness when agents already do useful work but a person still carries every result from one place to the next. Each manual boundary that repeats is a candidate for a system. Look for the moments where you explain the same context twice, or where work waits until you return to the computer.