Durable and public tool activity. Raw arguments, results, queries, titles, paths, and workspace content deliberately have no field in this type. The stable target ids and bounded public error summary are the only context kept for an auditable, useful activity row.
API reference sections
Schema
ToolDecisionResponse
Type object
Shape
| Field | Type | Description |
|---|---|---|
| activityrequired | ToolActivity |
{
"activity": {
"id": "00000000-0000-4000-8000-000000000000",
"attempt_id": "00000000-0000-4000-8000-000000000000",
"chat_id": "00000000-0000-4000-8000-000000000000",
"assistant_message_id": "00000000-0000-4000-8000-000000000000",
"tool_name": "string",
"read_only": false,
"status": "proposed",
"approval": "not_required",
"proposed_at": 0,
"started_at": 0,
"completed_at": 0,
"result_bytes": 0,
"error_code": "permission_denied",
"target_workspace_id": "00000000-0000-4000-8000-000000000000",
"target_document_id": "00000000-0000-4000-8000-000000000000",
"error_message": "string",
"agent_label": "string",
"agent_summary": "string",
"agent_input": "string",
"agent_output": "string",
"text_offset": 0,
"live": {
"choices": [
{
"id": "string",
"intent": "allow_once",
"label": "string"
}
],
"questions": [
{
"id": "string",
"header": "string",
"question": "string",
"options": [
{
"label": "string",
"description": "string"
}
],
"allow_other": false,
"secret": false
}
]
}
}
}The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.
Used by
POST
Approve a pending workspace-tool call/v1/ai/tool-calls/{tool}/approvePOST
Deny a pending workspace-tool call/v1/ai/tool-calls/{tool}/deny
Generated from contract version 1. Last updated .
