---
title: "The harness comes first"
updated: "2026-11-16"
url: "https://www.etheon.com/research/index/the-harness-comes-first"
authors: "Etheon"
published: "2026-11-16"
type: "research"
---

# The harness comes first

An agent harness is the software around a model that decides what the agent may do. We build the harness first and the agent inside it.

An agent is software that takes actions in your systems: it reads a task, calls the tools it is allowed to call and records every step. Building agents for clients has brought us to one conclusion about where its limits belong. They belong outside the model, in the harness around it.

## What a harness is

An agent harness is the software around a model that decides what the agent may do: the tools it may call, the permissions on each, the context it may read, where it runs, the steps a person approves and the log of every step.

## Its parts

- Model: reads the task and decides the next step.
- Tools: the actions the agent may call, each one named and limited.
- Permissions: what each tool may touch, enforced outside the model.
- Context: the documents and data the agent may read for this task.
- Sandbox: where the agent runs, apart from the systems it must not reach.
- Approval: the steps a person approves before they happen.
- Trace: every step written to a log your team can replay.

## Why it comes first

The model is one part; the harness around it decides what the agent may do. Limits enforced outside the model hold whatever the model answers. Safety is not a layer added at the end, so we build the harness first and the agent inside it.

## How we build one

1. Name every tool the agent may call.
2. Set each tool's permissions outside the model.
3. Run the agent in a sandbox, apart from your systems.
4. Put a person before the steps you choose.
5. Write every step to a log your team can replay.

Then we release in stages: first a person approves every action, then only the exceptions.