Start building with Computer Agents.
Create an API key, install the SDK, get a persistent computer, start a thread, and stream the work as agents execute inside a real workspace.
Start now
Create an API key, export it locally, and use the same credentials from SDKs or HTTP.
Create a persistent cloud computer where agents can browse, run code, and manage files.
Run a thread, send a task, or attach work to a project ticket with shared context.
Listen to execution events, logs, file changes, status updates, and final summaries.
What you can build
The SDK is the same control surface behind the Computer Agents platform. Use it from apps, scripts, services, notebooks, CI jobs, and internal tools.
Plan releases, create tasks, start task-linked threads, review work, and keep context connected.
Give agents files, packages, Git state, browser access, terminal access, and a workspace that survives sessions.
Deploy web apps, functions, databases, auth, agent runtimes, and secret vaults from the same workspace.
Run Metronome workflows, queue Batch jobs, schedule recurring work, trigger agents from events, and build your own control planes.
Combine Tests, Evaluations, assurance, optimization campaigns, and release control into auditable delivery systems.
Core concepts
Start with these primitives. Most workflows combine a computer, a thread, and optionally a project task or deployed resource.
Create and export an API key
Create an API key in Computer Agents, then export it so the SDK and direct HTTP requests can authenticate automatically.
Choose a cloud or appliance deployment
The same client targets Computer Agents Cloud and local appliances. Pass a deployment origin or an already-versioned /v1URL, then optionally scope all calls to one organization.
SDK URL normalization applies to regular requests, event streams, downloads, and multipart uploads. Direct HTTP calls always use the canonical /v1 prefix.
Install the SDK and run one task
The fastest path is run(). It creates the needed execution context, streams progress, and returns the final result.
Create a persistent computer and thread
Use this path when you want explicit control over the workspace. The same computer keeps files, installed packages, Git state, and runtime context across multiple thread turns.
Use projects when work needs team context
Projects give agents the surrounding plan: strategy, releases, backlog, comments, dependencies, resources, and review policy.
Deployable resources
Resources let humans and agents ship software from the same workspace where the work is planned and built.
Automate recurring and event-driven work
Use schedules, triggers, and orchestrations when agents should run without a person opening a chat.
SDK surface
After the quickstart, these managers are the main surfaces you will use to build real products and automation on top of Computer Agents.