67bc2370, reviewed October 20, 2026. It includes current typed execution/process/task
schemas and handler corrections to file routes, registration, authentication, and uncertain
execution results. It is not the complete billing/provider/internal route inventory.
Origin, authentication, and lifetime
Scopes, sandbox/task roles, current ownership, billing admission, and enabled features also
apply. A token or org header does not bypass those checks.
Choose a contract
Canonical files and safe outcomes
Use POST/GET/sandbox/{id}/files for writing/reading base64 bytes, and /files/list for
directory entries. The old reference paths /files/write and /files/read are retired.
HTTP 200 can carry outcome: unknown after a lost execution stream. Preserve original
execution/request identity instead of submitting a new command. record_pending and
execution_result_unconfirmed retain recovery evidence, not permission to retry blindly.
Accepted cancellation/stop is separate from observed process termination and cleanup.
The Computer Use API submits higher-level jobs;
Sandbox supplies lower-level runtime and desktop primitives. The SDKs,
workbench, and MCP
provide different client interfaces over these source contracts.