harness

The harness is the durable turn loop that wires session-manager, llm-router, and context-manager into an agent. A consumer stays thin: it kicks off a turn, renders the conversation from the session transcript, and reacts to turn boundaries and human-gated calls. The harness streams the assistant message into the session as it generates, so you watch the session, not the harness — there is no agent::events stream, and harness::status is a point-in-time recovery read, not a render feed.

Every invocation is a trigger (iii.trigger({ function_id, payload })); there is no separate "call" verb. Tool dispatch is deny-by-default: a send with no options.functions.allow is a plain chat loop and every model-requested call is refused until you allow globs per send. Sessions are minted by the harness (s_) or supplied by you; a send into a running turn folds in as steering (merged: true) instead of erroring, and a repeated idempotency_key returns the original turn without appending.

Prerequisites: session-manager (required — transcript store and change feed) and llm-router (required — generation and the model catalog) must be present. context-manager (token budgeting and compaction) is a soft dependency — absent it, the harness sends raw history. approval-gate (the human-in-the-loop gate) is optional; without it no call is held and every allowed call runs un-gated.

When to Use

• Start or steer an agent turn and return immediately (harness::send).
• Call an agent like a function, held open until the turn ends with the result returned inline and an optional output contract (harness::run).
• Cancel an in-flight turn (harness::stop) or read coarse turn state for recovery and guards (harness::status).
• Chain turns or react to outcomes by binding harness::turn-completed.
• Drive a turn from an arbitrary inbound event (cron tick, webhook, sensor) by translating it into a harness::send.

Boundaries

• Not a transcript feed. Render from session-manager's session::message-added / message-updated / status-changed (reconcile by revision); do not poll harness::status for content.
• Not the approvals engine. The harness ships only the gate mechanics; the policy, decision RPCs (approval::resolve), inbox (approval::list-pending), and prompt triggers live in approval-gate.
• Not a chain guard. options.max_turns bounds a single turn, not a send-completed-send loop; carry your own stop condition.
• Do not trigger the internal functions (below) — they forge call ids and turn progress, so calling them out of band corrupts the turn record.
• An in-run agent cannot start turns: send / run / turn / stop are denied to the model by policy. harness::spawn is the only model-reachable way to start a new turn, and it self-enforces depth, fan-out, and policy subsetting.

Functions

Consumer-facing:

• harness::send — ensure the session, persist the incoming message, and kick off a turn; returns fast or merges into a running turn (steering).
• harness::run — send held open until the turn ends; returns the turn result. The backend/automation entry point; supports an output contract.
• harness::stop — request cancellation of an in-flight turn; cascades to spawned children.
• harness::status — read the current turn state for a session; null when no turn ever ran. For recovery and guards, not rendering.
• harness::spawn — spawn a sub-agent in a child session. Model-facing (invoked through agent_trigger), not a consumer entry point.

Internal — the harness drives these; never trigger them directly: harness::turn (the durable loop step), harness::function::trigger / harness::function::resolve (dispatch and parked-call settle), harness::sweep-pending (cron expiry), and harness::on-config-change (hot-reload).

Reactive triggers

The harness emits two async turn-boundary trigger types so consumers and siblings react without polling harness::status:

• harness::turn-started — a turn began executing (first loop step).
• harness::turn-completed — a turn reached a terminal status (completed / cancelled / failed), carrying the result or error for chaining, failure toasts, auto-titling, and result delivery.

Bind turn-completed for outcomes and to chain the next hop; bind turn-started only for observability. Delivery is fire-and-forget, at-least-once, and unordered — treat each event as an edge. Nothing replays on reconnect: re-seed with harness::status and approval::list-pending, then rebind. Do not bind these for live transcript rendering — that is session-manager's job.

Binding config filters delivery by session_id, or by parent_session_id to watch the children a turn spawns.

How to bind

1. Register a handler: registerFunction('myapp::on-turn-done', handler).
2. Register the trigger:

iii.registerTrigger({
  type: 'harness::turn-completed',
  function_id: 'myapp::on-turn-done',
  config: { session_id: sessionId },
})

For the event payload shape, call get function info on the trigger type.

Hooks (policy siblings only)

The harness also registers five synchronous, in-path hook trigger types: harness::hook::pre-turn, harness::hook::pre-generate, harness::hook::post-generate, harness::hook::pre-trigger, and harness::hook::post-trigger. A bound hook runs in the turn's critical path and the harness acts on its return value (veto / hold / mutate) under a per-binding timeout_ms and on_error policy; pre-trigger / post-trigger bindings take a functions glob list to scope which calls they gate. These are for operator-trusted policy siblings (approval-gate binds pre-trigger); ordinary consumers do not bind hooks.