67bc2370, including candidate changes whose server
features may not yet be deployed. Discover actual capabilities and credentials before work.
Connect the right interface
API keys use
Authorization: ApiKey, JWTs use Bearer. Verified email, scopes, sandbox roles,
billing/admission and feature configuration apply. Requesting a tenant/runtime/region label
cannot grant authority or supply missing infrastructure.
Preserve the original work
Keep the exact supported request key/body/path before dispatch. Retain sandbox, execution, process, task/team and artifact IDs separately. Observe using original receipts after a lost response. Do not submit replacement creates, commands, teams, tunnel opens or file mutations merely because a client wait expired. A confirmed process exit establishes process status; inspect semantic task results separately.outcome_unknown, malformed receipts, missing exit codes, unconfirmed storage and truncated
output must remain explicit. Cancellation/stop acceptance does not prove worker termination.
Handle data and persistence
The Node file route is POST/GET/api/v1/sandbox/{id}/files; directory listing uses
/files/list. File bytes use base64. Upload multiline worker source as files instead of
hiding control characters in argv. Retain input hashes and verify collected outputs.
Persistent/durable workspaces preserve supported disk state until sandbox termination;
REPL/process RAM and active connections do not survive pod replacement. Export results into
artifacts or verified private bundles before expiry. Task registry grants do not grant
sandbox process access or reconstruct private control receipts.