Agent
A versioned config: model, prompt, tools, skills, MCP, harness. Sessions pin a version at creation; updates never rewrite live runs.
agent=model + skills + mcp
session=agent + env + vaults
1 · Configure
2 · Compose
3 · Run
4 · Reachoptional
The self-hosted agent platform for any LLM provider and any sandbox
Run your own agents on any model, in any sandbox. Deploy to Cloudflare Workers, or run it yourself with Docker.
Apache 2.0 · self-hostable · no vendor lock-in
Product
What Open Managed Agents is
A platform for running agent fleets, not a chat UI. Four primitives carry the whole model.
Session
A conversation backed by an append-only event log. Streaming, crash recovery, and lifecycle all hang off this durable state.
Environment
The execution sandbox: packages, network policy, container image. Reusable across agents, so a fleet shares one runtime shape.
Vault
A credential store that never enters the sandbox. An outbound proxy injects tokens at the network layer, matched by URL.
Example
See it run
Pick a use case and follow its trigger → agent → result pipeline, including the local bridge relay, Kubernetes, and the browser sandbox.
One agent, wired to your stack
Slackcustomer asks
agent
sandbox
skills: docs-lookup
memory
reply in-thread
Customer threads open sessions; answers are drafted from your docs.
Anatomy
What one request touches
Every message runs the same durable path. The session's append-only event log records it, the harness drives the model loop, tools execute in the sandbox, and the outbound proxy injects vault credentials the sandbox never sees.
- Request user.message (SSE)
- Session event log · DO-SQLite
- Harness model loop · tools
- Sandbox bash · read · write · MCP
- Vault proxy injects creds
The replayable event log is what makes a crashed turn resumable.
Reach
Any model, any sandbox
The control plane is the constant. Point it at Anthropic, any OpenAI-compatible gateway, or your own model; run tools on Cloudflare Containers, Kubernetes, an OpenShell bridge, a WASM VM in a browser tab, your own machine over the CLI, or a micro-VM vendor. In the middle, one durable spine owns context, state, and memory — so the session survives whichever model or sandbox you swap in.
Explore
Dig deeper
The details live on their own pages — pick a thread to pull.
How it works
→The meta-harness design, architecture layers, and the durable session lifecycle.
Features
→Everything the platform gives you — and why it's drop-in compatible.
Use cases
→Real workflows: ship code, run production, answer customers, work a thread.
Infrastructure
→Multi-agent fleets, any sandbox provider, and bridging your own machine.
Get started
Clone, deploy, or try the hosted deployment of the same codebase.