Agent harness
An agent harness runs the model. You keep the record.
A harness is the program around a model. It decides which tools the model may call, which calls need a person to approve, and what gets written down about each run.
MetaBot is a local harness. Each run asks before it writes. A call MetaBot classes as destructive waits for a person to approve it. When the run ends, MetaBot signs a receipt. A changed receipt reads INVALID when you check it.
What the harness does on a run
- It reads the work you point it at, in the folder you name.
- It asks before any write, unless you chose "Allow writes" for that run.
- A call it classes as destructive waits for a person to approve it.
- It records each step and its verdict, then signs the receipt.
What you can check yourself
- A dogfood run on MetaBot 0.4.0: a planted bug, a destructive call that was declined, and a receipt changed by one word, which read INVALID.
- The receipt check runs offline, with one command.
Claim pending: the proof rows behind these checks are not linked from this page yet.
Start with the one-line install:
uvx --from orcha-metabot metabot
What a run passes through
Questions
- How is a harness different from a model?
- A model writes text and proposes tool calls. A harness decides whether each call runs, asks you when it must, and keeps the record. You can change the model and keep the harness.
- How do I check a receipt?
- Run "uvx --from orcha-sdk orcha verify" on the receipt file. The check runs offline, with no server of ours. A changed receipt reads INVALID.
- What does a receipt not show?
- A check shows which key signed a receipt and that nothing in it changed since. It does not show that the steps happened.