Last verified: June 13, 2026
Anthropic ships four distinct ways to put Claude to work as an agent, and they are easy to confuse. The short version: Claude Cowork and Claude Code are interactive products billed through your Claude subscription — Cowork for knowledge work in the desktop app, Code for software work in your terminal, IDE, desktop, or browser. The Claude Agent SDK and Managed Agents are programmatic surfaces for developers, billed through the API: the Agent SDK is a Python/TypeScript library that runs the agent loop inside your own process, while Managed Agents is a REST API where Anthropic runs the loop and hosts the sandbox. The tables below give the verified, side-by-side breakdown.
The decision matrix
Each row is one surface. Read across for who it serves, whether you drive it turn-by-turn or hand it a goal, where the work executes, and how it is paid for.
| Surface | Who it is for | Interactive vs autonomous | Where it runs | How it is billed |
|---|---|---|---|---|
| Claude Cowork | Knowledge workers (non-developers) — research, documents, file and spreadsheet work | Interactive, supervised — shows you the plan and waits for your approval before acting | The Claude desktop app on your own computer (macOS or Windows); not available on web or mobile | Claude subscription (Pro, Max, Team, Enterprise) — draws from your plan’s usage allocation |
| Claude Code | Developers doing interactive coding — build features, fix bugs, automate dev tasks | Interactive — you drive it in a session, though it can run agentically across files and tools | Your machine (terminal, VS Code, JetBrains, desktop app) or the browser at claude.ai/code | Claude subscription or an Anthropic Console (API) account |
| Claude Agent SDK | Developers building custom agents programmatically (Python or TypeScript) | Autonomous — Claude reads files, runs commands, and edits code on its own via the agent loop | Your own process and infrastructure | API key (pay-as-you-go credits); see the subscription note below for the June 15, 2026 change |
| Managed Agents | Developers running production or long-running agents without operating their own sandbox/session infrastructure | Autonomous — you send events, Claude executes tools and streams back results | Anthropic-managed cloud sandbox per session (or a self-hosted sandbox on your own infrastructure) | Claude API key + the managed-agents-2026-04-01 beta header (no subscription path) |
Where billing actually differs
The cleanest way to split these four is by the wallet they draw from. The two interactive products are funded by a subscription; the two programmatic surfaces are funded by the API. This is the single distinction that trips people up most often, so it is worth stating plainly in its own table.
| Surface | Billing model | Notes |
|---|---|---|
| Claude Cowork | Subscription | Included on Pro, Max, Team, and Enterprise. Multi-step tasks consume more of your usage allocation than chatting. |
| Claude Code | Subscription or API | Most surfaces require a Claude subscription or a Console account; the terminal CLI and VS Code also support third-party providers. |
| Claude Agent SDK | API (pay-as-you-go) | Authenticated with an ANTHROPIC_API_KEY; also supports Bedrock, Claude Platform on AWS, Vertex AI, and Azure. Anthropic does not permit claude.ai login for third-party agents built on the SDK. |
| Managed Agents | API (credits) | Requires a Claude API key and the beta header; enabled by default for API accounts. |
One dated nuance is worth pinning down because it changes how subscription users pay for programmatic work. Starting June 15, 2026, Claude Agent SDK and claude -p usage on subscription plans no longer counts toward your Claude plan’s interactive usage limits; instead, eligible subscribers receive a separate monthly Agent SDK credit (per-user, not pooled), while subscription usage limits stay reserved for interactive use of Claude Code, Cowork, and Claude. If you use the Agent SDK with an API key from the Claude Platform, nothing changes — pay-as-you-go billing continues and you do not receive an Agent SDK monthly credit.
SDK vs Managed Agents: the programmatic split
Both programmatic surfaces let Claude run tools autonomously, but they differ in where the loop and the work live. Anthropic’s own comparison frames it this way: the Agent SDK “is a library that runs the agent loop inside your own process,” while Managed Agents “is a hosted REST API: Anthropic runs the agent and the sandbox, and your application sends events and streams back results.” Pick by who you want operating the infrastructure.
| Dimension | Agent SDK | Managed Agents |
|---|---|---|
| Runs in | Your process, your infrastructure | Anthropic-managed infrastructure |
| Interface | Python or TypeScript library | REST API |
| Agent works on | Files on your infrastructure | A managed sandbox per session |
| Session state | JSONL on your filesystem | Anthropic-hosted event log |
| Best for | Local prototyping; agents that work directly on your filesystem and services | Production agents without operating sandbox/session infrastructure; long-running, asynchronous sessions |
A common path, per Anthropic’s docs, is to prototype with the Agent SDK locally, then move to Managed Agents for production.
Quick chooser
If you are not writing code and want Claude to finish a task on your computer, use Cowork. If you are a developer working interactively on a codebase, use Claude Code. If you are building your own agent and want it to run in your own process, use the Agent SDK. If you want Anthropic to run the agent and host the sandbox for long-running or production work, use Managed Agents.
Is Claude Cowork the same as Claude Code?
No. Both appear in the Claude desktop app, but Cowork is aimed at knowledge work (research, documents, spreadsheets, file management) for non-developers, while Claude Code is an agentic coding tool. Cowork runs only in the desktop app (macOS or Windows); Claude Code also runs in the terminal, VS Code, JetBrains, and the browser.
Does a Claude subscription cover the Agent SDK or Managed Agents?
Cowork and Claude Code are included with Claude subscriptions (Pro, Max, Team, Enterprise). The Agent SDK and Managed Agents are API surfaces authenticated with a Claude API key. As of June 15, 2026, subscription users do get a separate monthly Agent SDK credit for SDK and claude -p usage, but Managed Agents has no subscription path — it requires an API key and a beta header.
Where does the work actually execute for each surface?
Cowork runs on your own computer in the desktop app. Claude Code runs on your machine (or in the browser). The Agent SDK runs in your own process and infrastructure. Managed Agents executes in an Anthropic-managed cloud sandbox per session, or a self-hosted sandbox you control.
Is the Agent SDK built on Claude Code?
Yes. Per Anthropic, the Agent SDK “gives you the same tools, agent loop, and context management that power Claude Code, programmable in Python and TypeScript.” Anthropic also describes it as “Claude Code as a library.”
Is Managed Agents generally available?
No. As of June 13, 2026, Claude Managed Agents is in beta. Every Managed Agents endpoint requires the managed-agents-2026-04-01 beta header (the SDK sets it automatically), and access is enabled by default for API accounts.
Leave a Reply