What is an agent harness?

import { agentJob, run } from '@obversa/runtime';
import { MockEngine } from '@obversa/runtime/testing';

const engine = new MockEngine(() => 'ready');

const job = agentJob({
  label: 'prepare-item',
  engine: 'offline',
  prompt: 'Prepare the item.',
});

const result = await run(job, {
  engine: 'offline',
  engines: { offline: engine },
});

console.log(result.outcome.status);

​

Inner and outer

​

Things that catch people out

• A harness does not review itself well. A second seat from a different provider catches what the first agrees with. The workflow is where that second seat is declared.
• Each call is fresh. Every engine call runs in a new process, so nothing leaks from one step to the next except what the workflow hands over. See engine plugins.
• The name is shared. Harness engineering, in this crowd, means building the inner loop. Obversa is the layer above it. See what is a meta-harness.

​

Where to go