Never offered
Destructive and ungraded tools are filtered out of the listing the model sees.
Offered, then checked
Read and write tools are listed, and every call still needs authority captured while a person was present.
No authority
The call parks and the run answers interrupted, carrying the card.
Put those cards in front of a person, then carry on where the run stopped:
```ts focus={4} theme={null}
const result = await support.run(task, { as: subject });
if (result.status === "interrupted") {
const done = await result.resume({ [result.interruptions[0]!.id]: "approve" });
}
```
`resume()` is not a rerun. The turn picks up byte for byte from where it
parked, and a denied call is a refusal the model reads and works around.
The result channel is the one exception. It reaches nothing, so it is never
guarded and never parks, which is what keeps a typed run from stranding on a
card nobody can answer.
## Meter on usage
Every result carries the run's token totals. This is the number to bill and
budget on.
```ts focus={3,5-9} theme={null}
const result = await support.run(task, { as: subject, output: Triage });
if (result.status !== "error") {
await meter.record(ownerId, {
input: result.usage.inputTokens,
output: result.usage.outputTokens,
cacheRead: result.usage.cacheReadTokens ?? 0,
cacheWrite: result.usage.cacheWriteTokens ?? 0,
model: result.usage.model,
});
}
```
A turn that broke never reached a model, so `usage` is on the three statuses
that ran and the `error` check is what types it. `cacheReadTokens`,
`cacheWriteTokens`, and `model` are optional on `TurnUsage`; the two token
counts are always there. The same figures land on the run's audit rows in your
Cloud console.
## Cancel it
There is no `cancel()`. Cancellation is an `AbortSignal`, the same as
everywhere else on the platform.
```ts focus={3} theme={null}
const result = await support.run(task, {
as: subject,
signal: AbortSignal.timeout(60_000),
});
// result.status === "stopped", result.reason === "aborted"
```
An aborted run still answers. What it said, the calls it made, and the usage it
spent are all preserved.
## What the result carries
Four ends and no fifth. Read `status` once, and every field you then touch is
there.
| `status` | Also carries |
| ------------- | ---------------------------------------------------- |
| `ok` | `output`, the typed value when you asked for one |
| `interrupted` | `interruptions`, and `resume(decisions)` to carry on |
| `stopped` | `reason`, either `"aborted"` or `"maxToolCalls"` |
| `error` | `error: { code, message }`, and `text` is empty |
And the run itself:
| Field | Type | What it holds |
| ----------- | -------------------------- | -------------------------------------------------------- |
| `text` | `string` | The model's own words — what it actually said |
| `threadId` | `string` | The conversation this run wrote to |
| `turnId` | `string` | This turn, stable across a park and a resume |
| `toolCalls` | `Array<{ call, outcome }>` | Every call attempted, in order, with the guard's outcome |
| `usage` | `TurnUsage` | Token totals for the whole run |
`text`, `threadId` and `turnId` are on all four arms. `toolCalls` and `usage`
are on the three that ran: a turn that broke never spoke, so `error` carries
the failure and an empty `text` instead of a sentence in the agent's voice.
## Options
| Option | Type | Default |
| -------------- | ------------------------- | --------------------------------------------- |
| `as` | `string` | The agent's own subject, `vendo:agent: