OpenClaw
The BeeOS Claw plugin connects OpenClaw to the platform while retaining its native engine.
For developers and teams · Developer preview
Your agents.
Working in your world.
An open platform for agent applications and execution. Bring your agent, connect it to real systems, and build it into your product—across cloud, private environments and local hosts.
Developer preview. Runtime access, regions and tools depend on the integrations enabled in your environment.
Your agent, your execution loop
OpenClaw · Hermes · Custom agents · Device Agent
Plugin or SDK integration
BeeOS Cloud
Manage resources, authorize access and connect tools.
Cloud
Private cluster
Local host
The runtime executes the work. Available capabilities depend on its adapter and connected resources.
How it works
Connect what you have. Build what comes next.
- 01
Bring your agent
Use a supported integration or connect your own agent through the SDK. Keep your reasoning and execution logic.
- 02
Choose where it runs
Connect cloud resources, a private cluster or a local host. Choose an environment that supports the task.
- 03
Connect real systems
Use APIs, MCP tools and supported device controls with the access each task needs.
- 04
Deliver it in your product
Connect your backend through the Server API and SDK. Receive lifecycle webhooks and present results in your own application.
Run your agent
Keep the engine you choose.
Open integration means room for different frameworks and execution models. Each runtime keeps its own reasoning, tools and collaboration behavior.
These are integration paths, not a universal compatibility guarantee. Check adapter support and declared capabilities before choosing a runtime.
Hermes
An independent runtime with its own execution model and platform integration.
Custom agent + SDK
Bring your own execution loop. Implement and declare the capabilities your agent supports; installing the SDK does not add them automatically.
Device Agent
Run on a host and connect to device services for desktop or Android control. The host and the controlled device have distinct roles.
Beyond a chat reply
Give work somewhere to happen.
Combine the capabilities your runtime supports. These examples describe execution patterns; availability follows the enabled adapter, tool and resource.
Work across services
Read data through an API, use an authorized MCP tool and return a useful result to your application.
Managed MCP connections and a runtime’s native tools are separate integrations.
Operate a real interface
Use a supported browser, desktop or Android environment. Observe progress and take over when the session grants control.
Viewing and control have separate permissions. Device and media support depend on the runtime.
Execute code. Deliver files.
Run scripts in a capable execution environment, process data and produce files or artifacts your product can present.
Code execution, workspace files and interactive output each require corresponding runtime support.
Your product. Clear responsibilities.
Build your own application on the same platform foundation as BeeOS App. Keep product decisions close to your users.
- Cloud manages platform resources
- Organizations, Apps, scoped access and resource management. Skills catalogs, MCP connections and operational events support platform operations as they become available.
- The runtime does the work
- It runs inference and tools with its configured model services. Skills installation and execution belong to the runtime.
- Your backend owns your users
- Keep user identity, permissions and subscription entitlements in your product. Store server credentials on the backend; use your own user channels and purpose-bound connections for live sessions.
Start with one integration
From your agent to your application.
Explore the Console for developer access, organizations and Apps. Review the integration guide and confirm the capabilities available in your environment before connecting a runtime.