RESOURCES / OPENCLAW

Understand the runtime underneath the AgentOS operating layer.

AgentOS is the human control surface for workspaces, workers, tasks and supervision. OpenClaw is the Gateway-based runtime that owns agent execution, sessions, models, channels, tools and browser capabilities.

AgentOSOpenClaw GatewayModels, tools and channels
RESPONSIBILITY BOUNDARIES
Human operatorSets direction, reviews outputs and handles consequential decisions.
AgentOSOrganizes workers and workspaces, dispatches work, presents state and diagnostics.
OpenClaw GatewayOwns runtime execution, sessions, models, channels, tools and supported capabilities.
Connected resourcesUser-selected providers, accounts, integrations, channels and browser runtime.
WHAT TO EXPECT

Gateway-first, with explicit limits.

Available through AgentOS

AgentOS can connect to a live Gateway, project real state, organize worker and workspace configuration, and expose runtime health, compatibility and supported methods.

Available through OpenClaw

Gateway execution, sessions, channels, automations, model access and browser profiles are runtime capabilities. Their availability depends on the configured Gateway and provider setup.

Advanced or incomplete behavior

Accounts and browser profiles are an MVP bridge; typed browser-profile dispatch is not yet exposed by OpenClaw. Account rules that require approval remain blocked until approval dispatch exists.

Hosted and local runtime considerations

In the documented Railway deployment, the Gateway stays on container loopback and the supervisor manages its lifecycle. For a deliberately remote operator setup, AgentOS blocks remote Gateway URLs by default unless explicitly enabled; use HTTPS, authentication and exact trusted origins. Do not expose source or package installs publicly without an appropriate network boundary and monitoring.

Use runtime diagnostics before assigning real work.

A ready model, a reachable Gateway and a scoped workspace are the minimum useful starting point.

Read the Quickstart