Skip to main content
Version 1.1.0 provides a typed Python SDK over the daemon HTTP API. Choose an entry point based on who owns the desktop lifecycle.

Choose an entry point

Use the async surface when your application already uses asyncio:
The sync and async entry points expose parallel namespace methods. Async methods add await but keep the same operation names and result models.

Reference map

Configuration

Review public SDK models, defaults, and environment ownership.

Namespaces

Find each desktop operation by namespace.

Errors and models

Identify stable result models and failure types.

OpenAPI

Inspect the checked-in daemon schema and route groups.

Import boundary

Import stable top-level SDK types from modal_computer_use.
Core imports do not require Modal, OpenAI, Anthropic, or provider credentials. Install the modal extra before you enter a Modal provisioning or attachment context.

Daemon boundary

The daemon exposes health, readiness, version, capability, and /v1/* primitive routes. The Python clients own connection pooling and typed serialization. They do not add a provider-owned model loop. Use OpenAPI when you need the HTTP contract. Use Namespaces when you write Python. The v1.1.0 API guide records lifecycle, handoff, action, and provider-adapter contracts.