OpenAI Computer Use: capabilities, evidence & fit
A model capability for deciding browser and desktop actions in an environment you control.
The decision layer. Your application supplies a browser or desktop, executes returned actions, captures the next screenshot, and enforces approval boundaries. Pair it with execution infrastructure or a local sandbox.
- Last verified
- Sep 27, 2026
- Primary sources
- 3
- Evidence state
- Fresh
- Benchmark records
- No linked results
Where it fits
- Custom browser and desktop agent loops
- Teams already using the Responses API
- You need a ready-made hosted browser
- A stable application API already covers the workflow
Fit recommendations are editorial interpretations of the documented architecture.
Documented capabilities
| CAPABILITY | DOCUMENTED STATE | SOURCE |
|---|---|---|
| Control surfaces | Browser and desktop interfaces | |
| Perception | Screenshots and tool results guide the next action | |
| Action interface | Structured mouse and keyboard actions | |
| Code path | Code execution can use Playwright or PyAutoGUI | |
| Execution ownership | The developer supplies and controls action execution | |
| Integration reference | Official sample application is publicly available |
Environment, deployment & control
Environment
- browser
- Full
- desktop
- Full
- mobile
- Unknown
Deployment
- cloud
- Full
- local
- Unknown
- self Hosted
- Unknown
Extensibility
- api
- Full
- sdk
- Full
- mcp
- Unknown
- bring Your Own Model
- Unknown
Control method
- screenshots
- Full
- mouse Keyboard
- Full
- dom Or Accessibility
- Unknown
- code Execution
- Full
Unknown = insufficient public evidence; No evidence = an explicit negative record; N/A = does not apply to this layer.
Trust, oversight & limitations
Documented oversight
- human Approval
- Unknown
- audit Logs
- Unknown
- sandboxing
- Unknown
- prompt Injection Defense
- Unknown
- credential Controls
- Unknown
Know the boundary
- The API does not itself supply your application's execution environment.
- Untrusted screen content can contain instructions; sandboxing and consequential-action approval remain application responsibilities.
Pricing snapshot
$10 / 1M input tokens · gpt-6-astra
gpt-6-astra · Standard · short context
Verified Sep 27, 2026 · USD · usage. Hosted services and software licensing can have different terms.
Cost inputs & calculator →Compare the tradeoffs
OpenAI Computer Use vs Claude Computer Use
Both provide model-side computer-use capabilities. The decision is which provider integration and action surface fit your runtime; neither comparison entry includes the surrounding production system.
OpenAI Computer Use vs Gemini Computer Use
Compare execution contracts and required environments first. Public capability scope does not establish that either integration completes your workflow more reliably.
Relevant use cases
Sources & verification
Reviewed Sep 27, 2026. Architecture recommendations are editorial analysis; linked vendor documentation supports the underlying capability and safety facts.
- developers.openai.com/api/docs/guides/tools-computer-use
- developers.openai.com/api/docs/pricing
- github.com/openai/openai-cua-sample-app