Build Computer Agents into your own product.
Use the JavaScript and Python SDKs to run agents, control persistent computers, manage project work, deploy product resources, stream progress, and operate Computer Agents from your own applications.
Start threads, stream work, resume sessions, approve permissions, and collect feedback.
Create persistent cloud computers, manage files, install packages, and keep workspace state.
Deploy web apps, functions, databases, auth, runtimes, and secrets from code or agents.
Listen to execution events, logs, file changes, status updates, and final summaries.
Language SDKs
Start with the language your product already uses. Both SDKs expose the same platform concepts and resource managers.
Use one typed Node and TypeScript client for threads, tasks, computers, web apps, functions, auth, databases, feedback, notifications, runtime helpers, and automation.
Automate Computer Agents from scripts, services, notebooks, CI jobs, research pipelines, and backend systems with the same platform surface.
SDK surface
The SDKs are product clients, not thin wrappers around one endpoint. Use them to operate the full Computer Agents workspace.
| Threads and runs | Create threads, send messages, stream events, inspect logs and diffs, cancel runs, resume work, and collect feedback. |
|---|---|
| Computers and files | Create persistent computers, choose compute profiles, upload files, download folders, manage Git-aware workspaces, and reuse state across sessions. |
| Projects and tasks | Create projects, releases, tickets, comments, task-linked threads, review flows, and shared execution context. |
| Deployable resources | Create, deploy, invoke, bind, monitor, roll back, and operate web apps, functions, databases, auth, runtimes, and secrets. |
| Automation | Manage skills, schedules, triggers, orchestrations, product notifications, permission requests, budget, and usage data. |
Resource managers
Work directly with deployed product surfaces instead of setting generic resource kinds by hand.
| Web apps | Hosted dashboards, portals, internal tools, AI apps, and prototypes with custom domains and bindings. |
|---|---|
| Functions | HTTP APIs, webhooks, scheduled jobs, data transforms, and backend actions deployed from a workspace. |
| Databases | Database lifecycle, collections, documents, JSON records, bindings, and operational metadata. |
| Auth | Sign-up, sign-in, sessions, user administration, protected flows, and identity-aware app resources. |
| Secrets | Secret vaults for API keys, credentials, tokens, and runtime-only configuration. |
| Agent runtimes | Always-on agent APIs, embedded assistants, operational copilots, and managed runtime endpoints. |
| Skills and automation | Publish skills and drive ACP with schedules, triggers, and orchestrations from the SDK. |
First run
The same idea works in both SDKs: create a client, run a task, stream events, and keep the resulting thread for later.
SDKs and raw HTTP
Use SDK guides for product workflows. Use the generated API reference when you need exact request and response schemas.
| SDK guides | Best for application code, typed resource managers, runtime helpers, and product-oriented workflows. |
|---|---|
| API reference | Best for raw HTTP integrations, schema-level implementation, generated clients, and language-agnostic systems. |
| Quickstart | Best when you want the shortest path from API key to first persistent computer, thread, task, and deployed resource. |