Operator documentation
Write a bounded coding mission
Define inputs, output and acceptance checks before starting an Operator workspace.
Specify the deliverable
A good mission names the repository or approved input, the files that may change and the result you expect. For a public-data task, include the schema and the source date. Avoid asking for a broad repair without an observable completion condition.
- Name the input and allowed scope.
- Describe the expected artifact.
- Write the checks that establish completion.
Keep execution bounded
Operator provides isolated remote Claude Code or Codex workspaces using your own provider subscription. Trial runs are limited to 30 minutes and paid runs to 60 minutes. Divide work so that one mission has a reviewable result within the relevant limit.
Review before reuse
Inspect the returned changes, tests and receipt. A run completing does not establish that the result is deployed or accepted in your production environment.
Continue
Reviewed September 17, 2026. Current product terms and availability are listed on the product site.