Self-hosted Claude Managed Agents keeps agent credentials in your environment
Anthropic releases self-hosted Claude Managed Agents for private beta.
Anthropic has launched a self-hosted version of Claude Managed Agents in private beta, allowing companies to run agent harnesses, sandboxes, credentials, and session history on-premise or in their own cloud environments. This new option enables customers to manage sensitive credentials within their own secrets managers, enhancing control over unattended agents. The system is built around four security principles, including separating the harness from the sandbox and using allowlists for hosts, with logs exportable via OpenTelemetry for monitoring.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Google?
Get an email when a new story names Google, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonAnthropic's self-hosted Claude Managed Agents offering highlights a critical shift in responsibility: when agent harnesses, sandboxes, and credentials move into a customer's own environment, that customer now owns the security of those assets. If credentials stored in internal secrets managers are misconfigured, over-permissioned, or inadequately audited, unattended agents can become a high-value attack vector with little human oversight. The architecture's emphasis on separating harnesses from sandboxes and using host allowlists reflects sound design principles, but those controls only work if operators implement and maintain them correctly. This matters because agentic AI systems often act autonomously over extended periods, meaning a compromised credential can cause significant damage before anyone notices.
What helps against this
How we list vendors- Privileged access management (PAM)
Admin accounts stop being one stolen password away from control of everything.
- Secrets management
API keys, tokens and passwords stop leaking from code, chat and configuration files.
- Security monitoring (SIEM)
Logs from everywhere end up in one place, with alerts that someone actually sees.