Skip to main content
Operator is the control layer for hosted OpenClaw agents. Use the manager in the web app or call the same control surface through the API. Operator provisions, configures, and manages the instances for you.

​
What Operator is

Operator has two entry points:
  • Web app: chat with the Operator manager
  • API: send the same requests programmatically
The manager can:
  • create, restart, delete, clone, and inspect instances
  • install skills and update agent files and config
  • grant secrets and verify access
  • message running agents
  • schedule manager automations and handle webhooks
Operator also runs the infrastructure underneath each instance, so you do not need to manage servers or storage yourself.

Quickstart

Create your first agent, connect a channel, and add the secrets it needs.

Instances

Learn the difference between prebuilt, bare, and checkpoint based instances.

Automations

Run recurring manager level tasks on a cron schedule.

Webhooks

Trigger the Operator manager from external systems.

Environment

Store secrets securely and grant them globally or per instance.

Integrations

Connect GitHub, Resend, PostgreSQL, Cloudflare, Vercel, X, and more.

API

Authenticate, call /api/chat, and work with Operator programmatically.

Settings

Manage plans, billing, and API keys.

​
How work runs in Operator

Operator has three execution paths. Keeping them separate avoids most setup mistakes.
  1. Run now in an instance Use this when one agent should do something immediately. Example: inspect a repo, send an email, or update a config file.
  2. Recurring work inside an instance Use this when the schedule belongs to one instance. This is local cron inside the agent environment, not a manager automation.
  3. Manager level automation Use this when Operator itself should run a recurring task across your fleet. Example: restart all active instances every night, review recent activity, or generate a daily report.
If you want recurring work but are not sure where it should live, decide whether the schedule belongs to one instance or to the Operator manager.

​
What Operator manages for you

  • Container provisioning and restarts
  • Managed model access and search routing
  • Encrypted config storage
  • Secure secret storage and per instance grants
  • Chat based fleet operations
  • Scheduled automations and webhook triggers

​
Next steps

Start with Quickstart. Then read Instances and Environment. If you plan to drive Operator from code, go to API.