Approvals

Approval policy belongs to modes and tools. Tool metadata can request approval, and the host resolves pending approval handles when a request is surfaced to a user.

Tool Metadata

class WriteReportTool extends HarnessTool<WriteReportInput> {
  name = "write_report";
  description = "Write a report file.";
  schema = writeReportSchema;
  risk = "write" as const;
  permissions = [{ kind: "filesystem" as const, access: "write" as const, path: "." }];
  requiresApproval = true;
  approvalTimeoutMs = 60_000;

  async execute(args, session) {
    return { content: "Wrote report.md" };
  }
}

The tool belongs to a mode. requiresApproval is a behavior hint, and approvalTimeoutMs controls how long a pending request can wait.

Mode Policy

class ReviewMode extends HarnessMode {
  toolApproval = "ask" as const;
  tools = [new WriteReportTool()];
}

Policies are auto, ask, deny, and tool-default.

Resolve Pending Approvals

const stream = await store.stream("approval-demo", "Write the report.");

for await (const event of stream) {
  if (event.type === "tool.approval.requested") {
    await event.approval.approve();
  }
}

You can also resolve through the store:

const [approval] = store.getPendingApprovals("approval-demo");
await store.approveTool("approval-demo", approval.id);
await store.denyTool("approval-demo", approval.id, "Not allowed in this environment.");

Approval request and resolution events are available through streams, session listeners, event queries, logs, and storage.