The control center can bring its own model and can host several agent implementations through ACP-compatible backends.
OpenHands/OpenHands
A self-hosted developer control center that can run OpenHands and other ACP-compatible coding agents across local, Docker, remote, and cloud backends.
Individuals and teams hosting persistent coding agents and automations.
Agent Canvas / agent and automation servers / local, Docker, remote, and cloud backends
The executor boundary changes with the selected backend
The same control surface can connect to an agent running directly on a host, in Docker, on a VM, or in a cloud service; the README explicitly warns that an unsandboxed server has full filesystem access.
System Map
Eight inspection boundariesConversations, project mounts, automations, and backend-owned state shape durable work.
Agent Servers execute work on a selected local, container, VM, remote, or cloud environment.
Isolation depends materially on backend choice; direct host execution and Docker mounts carry different authority.
Always-on servers and switchable backends make continuity a service-level concern.
Automations and issue decomposition coordinate work; agent-specific worker semantics depend on the selected backend.
Agent Canvas centralizes conversations, backend choice, automations, and team operation.
Architecture docs, deployment commands, warnings, backend APIs, tests, and future source reporting expose the control plane.
Learn Through This Project
10 lessonsLatest Reporting
0 articlesNo Daily Edition reporting is attached yet.
Primary Sources
Open Questions
- Can the UI make the effective backend authority and isolation level impossible to miss before work begins?
Evidence state describes what this Atlas profile can support today. It is not a product score and it is not evidence that uninspected capabilities are absent.