Claude Managed Agents x Notte: What the Sandbox Can't Reach

Claude Managed Agents can use a Notte session to navigate websites, fill forms, and extract data. Both the agent and browser run on managed infrastructure, and both can run on a schedule.

The browser Claude doesn't have

Claude Managed Agents is Anthropic's hosted runtime. Anthropic provisions the container and agent loop; you provide the environment and prompt. The sandbox has bash and file tools, so the agent can install packages and call APIs.

Some jobs still require a browser. An agent may need to download an invoice from a vendor portal, check a signup flow while logged out, or use a site with no API. These jobs also fail in less predictable ways than API calls: pages move, sessions expire, and UI state can be easy to misread.

To connect Notte, add your Notte API key to Anthropic's credential vault and install the Notte CLI in the agent environment. The agent can then start browser sessions, open pages, interact with them, and extract data. The sandbox contains a placeholder for the key; Anthropic adds the real value at the network boundary, outside the model's context.

"The agent never sees your key because the sandbox only holds a placeholder. The real key is attached at the network boundary, and only on requests to domains you allow, so it only goes where you've approved."

Anthropic, New in Claude Managed Agents

Sessions come with stealth mode, CAPTCHA solving, proxy routing by country, and profiles that persist browser state between runs.

What you can build

For a broad site audit, assign a page to each subagent and combine the results. When we ran this on our own site, the agent found a 56-term glossary with no search, a sign-in page with no link to sign up, and broken compliance links in the trust center.

The same pattern works for company research. Subagents can check pricing, usage limits, customer pages, and job listings in parallel.

You can also run a nightly job that logs into a vendor portal and sends the results to your system of record. Managed Agents handles the schedule. Vaults store credentials, while Managed Auth maintains third-party logins and re-authenticates when needed. A Notte persona adds an inbox and phone number for flows that require email or SMS verification.

When the model leaves the loop

Once a browser flow is stable, notte functions create turns it into a serverless endpoint. You can call it over HTTP, trigger it with a webhook, or run it on a schedule. Repeated runs no longer need the model, which cuts token use and makes the behavior more predictable.

Why use Notte

Cloud browser APIs look similar on paper. In practice, startup time matters because a Managed Agent may open several browser sessions during a run. Each slow connection holds up the agent.

We built Browser Arena to measure this. It runs seven cloud browser providers through the same test on the same machines: create a session, connect over CDP, navigate, and release. Notte connects in 353ms and costs $0.00 per hour. The benchmark and test harness are public, so you can check the results or run it yourself.