Check whether an Anthropic Managed Agents client can run on Awaken

Use this page before changing an existing Anthropic Managed Agents client. Name the SDK version and resource family you use, then choose one of the four outcomes below. Do not treat “the request reached the server” as proof that the whole client is compatible.

Make the compatibility decision first

The current validation record covers @anthropic-ai/sdk 0.122.0 and Python anthropic 1.2.0. Both expose 127 generated operations in the reviewed Managed surface. The TypeScript matrix also exercises 0.121.0, 0.117.1, and 0.105.0; the Python matrix covers every selected change point from 0.92.0 through 1.2.0. These are tested versions, not dependency requirements. Choose versions under your own dependency policy, then use this page to see what was actually exercised. At Awaken revision 50d5035c68456c9106626f748cf4c169c2057beb, the operation manifest maps all 127 current SDK methods and 12 reviewed SDK-absent documented routes to named executable scenarios. Compatibility applies only to the named paths, methods, DTOs, errors, helpers, and constraints on this page.

Connect the official SDK

import Anthropic from '@anthropic-ai/sdk';

const client = new Anthropic({
  baseURL: 'http://localhost:8080',
  apiKey: process.env.AWAKEN_API_KEY ?? 'local',
});

const session = await client.beta.sessions.create({
  agent: process.env.AWAKEN_AGENT_ID,
  environment_id: process.env.AWAKEN_ENVIRONMENT_ID,
});
await client.beta.sessions.events.send(session.id, {
  events: [{
    type: 'user.message',
    content: [{ type: 'text', text: 'Summarize RFC 8259.' }],
  }],
});

Changing the base URL is not the only integration change: configure Awaken authentication. Official Managed resource methods add their required beta selector. Raw HTTP clients must send it themselves. Awaken accepts x-api-key: <token> or Authorization: Bearer <token>.

Before migrating the full application:

1. Record the SDK version you chose and find every resource family the client calls.
2. Set baseURL and Awaken authentication; confirm the SDK method adds the expected beta selector.
3. Create one Session, send one event, and inspect the returned error envelope.
4. Apply every constraint used by the application, then test its retry and archive paths.

How to use the design references

This page is the single public owner of compatibility and divergence claims. The Managed Agents protocol page only explains how this wire enters the runtime. Each meaningful constraint below links to the page that explains its ownership, state changes, failure handling, and deployment responsibility. That design page explains why the behavior exists; this page remains the place to decide whether a client can use it.

SDK validation matrix

This matrix is worth publishing because “SDK compatible” has more than one failure mode. A route can exist while a generated method, helper, retry rule, stream decoder, or response DTO still differs. The matrix shows which client and behavior were tested, while the resource matrix below answers which API family an application can use.

Use Anthropic’s Managed Agents overview, Session operations, and the official TypeScript and Python SDK repositories as the upstream reference. This page records Awaken’s tested projection and differences; it does not replace those sources.

Beta-header decision table

The server parses comma-separated values and repeated anthropic-beta headers. Missing a required beta returns a Managed invalid_request_error.

The Dreams SDK methods add the dreaming beta themselves. Awaken accepts that generated request without requiring the Managed beta on /v1/dreams.

Compatibility matrix

“Compatible” applies to the named wire contract. Model availability, credentials, sandbox capacity, and backend placement are Awaken configuration concerns and can still cause a valid request to fail explicitly.

Known differences and constraints

Awaken extensions

Extensions share the same governed objects, but are not part of the Anthropic baseline. Most use distinct route families:

A small number of extensions intentionally sit beside or inside compatible shapes and therefore must be handled explicitly by strict clients:

These fields and routes are extensions; a client that wants only baseline behavior should not send or depend on them. The canonical application route-family index is API reference.

Execution extensions: Native, ACP, and A2A

The compatible wire does not fix the execution backend. An immutable published model binding selects one of:

• a Native in-process backend;
• a supported ACP CLI backend such as Claude Code, Codex, Gemini, OpenCode, or Hermes;
• a remote A2A endpoint.

ACP runtime choice is separate from sandbox placement (local, namespace, docker, podman, or k8s). Exact model selection, credential delivery, and session persistence differ by ACP implementation. See Select models and ACP runtimes through the API for selectors and publication boundaries, then the ACP runtime matrix for per-runtime differences.