self-hosted-sandboxes-custom-tools changedmanaged-agents/self-hosted-sandboxes-custom-tools
Nearest release: v2.1.322, published 2 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−0removed
From line
6
where the diff opens
First seen
2 Oct 2026
this site's first read of the page
Recorded edits16to this page, all time
The whole hunk
from line 6, old and new numbered
/
from line 6
66 topic:
77 title: Managed Agents
88 url: https://platform.claude.com/docs/en/managed-agents/overview
9 status: beta
910 betaHeader: managed-agents-2026-04-01
1011 zdr:
1112 eligibility: not-eligible
from line 31
3031 - claude-sonnet-4-6
3132 - claude-opus-4-5-20251101
3233 - claude-sonnet-4-5-20250929
34 supportedPlatforms:
35 Claude API: beta
36 Claude Platform on AWS: beta
37 Claude Models on Google Cloud (Anthropic managed): beta
3338---
3439
3540[Custom tools](https://platform.claude.com/docs/en/managed-agents/tools#custom-tools) are tools your own code runs: the agent emits an `agent.custom_tool_use` event and waits for a matching `user.custom_tool_result`. Your worker can be that code. Because it runs inside your sandbox, the tool reaches the internal services, credentials, and network egress you configured for the sandbox, and nothing more.
No line in this hunk matches that.