Skip to main content
Telara
Claude Managed Agents logo

Claude Managed Agents

Claude Managed Agents (Anthropic Messages platform, beta) as a governed handoff destination. A receiver provisions an agent that carries only an MCP toolset, and an environment, in their own Anthropic workspace. Telara creates one empty vault per run, stores the handoff grant session bearer in it, and only then creates the session with the grant session as its only MCP server and the approved brief as its first message, so every request Anthropic makes to the grant session is authenticated. At the end it deletes the vault with its credential and the session with its history. This definition is the configuration to qualify, not evidence that it has been qualified.

Capability matrix

Indexes NoTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events No

Prerequisites

An Anthropic workspace API key owned by the person who will receive the work, and an agent and an environment already created in that workspace.
Permission to attach the agent to Telara as a handoff destination.

Get the credential

1
Add the workspace key
Add the Anthropic workspace API key to Telara as your own credential. Telara checks which organization the key belongs to before it offers the destination.
2
Register the agent and environment
Register the agent id and the environment id as the destination's runtime, written as the agent id, a slash, and the environment id.

Connect in Telara

API key

Anthropic workspace API key (prefix sk-ant-api). It must belong to the workspace that holds the receiver's agent, environment and vault. An Admin API key is not accepted.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Known limitations

Telara starts a run only after the receiver approves it, and it deletes the run's vault and session when the work ends or is stopped. Nothing from the run stays at Anthropic.
A run whose start acknowledgement is lost is held for review. Telara never starts a second one on its own.
The destination is offered only after this configuration has been qualified.