Computer use with OpenAI models

The Python ComputerTool and the TypeScript adapters/openai export translate a computer-action protocol into the same desktop API. The adapter, not a guessed model version, defines the accepted action shapes. A runnable live-provider loop is not shown here. Not installable yet; available when the beta opens.

Safety checks are an application decision

Supply a safety_check_callback for pending safety checks. The adapter passes a copy of the pending checks to that callback; your application must approve deliberately. The absence of approval is not consent. Unsupported actions raise UnsupportedAction; pending checks raise SafetyCheckPending; a failed action raises ComputerActionFailed with the failed index and executed count. Do not catch one of these and then continue executing the remaining actions from the same model turn.

Keep the interaction bounded

Keep the Dory API key and your model-provider key in the local client. Set a finite model-turn limit and a computer run deadline, keep the computer ID before starting work, and close streams before a bounded pause or stop. A successful local SDK return does not prove that an external browser works as expected.

Use human takeover when a person must act. Prefer view-only observation when exclusive control is unnecessary. An agent must not set force merely to bypass human_in_control. The Python and TypeScript SDK pages describe the adapters, including synchronous versus asynchronous execution.

Preview action shapes

The unverified_action_shapes option accepts the preview action shapes supported by the adapter. It is not a general bypass for unknown actions.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.