Sync existing OpenClaw agents
Bring running OpenClaw agents into ClawControl without recreating them from scratch.
Use agent sync when you already have OpenClaw agents running and want ClawControl to discover, review, and adopt them into Mission Control.
What sync does
When you open the sync flow, ClawControl scans one connected runtime and shows a preview before it changes anything.
That preview helps you answer three questions:
- Is this agent new to ClawControl, or is it already managed?
- Does this runtime own the agent, or is it managed somewhere else?
- Should the next step be import, reconcile, or no action?
This makes sync safer than blindly importing everything on a machine.
What ClawControl checks during preview
The preview is not just a name list. It inspects the parts of an OpenClaw agent that matter for Mission Control.
Typical checks include:
- agent identity, default status, and likely role
- whether the Mission Control plugin is enabled
- whether auth looks ready on that agent
- templates and key files such as
SOUL.md - model defaults and behavior defaults
- recurring schedules and custom cron jobs
- whether the agent is already managed on this runtime or another one
What the recommended actions mean
| Recommended action | What it means |
|---|---|
| Import + Adopt | The agent is not yet managed by ClawControl on this runtime, so it can be brought under management. |
| Reconcile | The agent is already managed on this runtime, but ClawControl found differences worth updating. |
| No Action | The agent is already aligned, should not be changed from here, or needs manual review before sync. |
Why some agents need manual review first
Default agents and likely LEAD agents deserve extra care.
If ClawControl detects that a default agent is likely to act as a LEAD but its
SOUL.md does not clearly support LEAD behavior, auto-import may pause so you
can review it first.
That matters because LEAD agents usually coordinate work, synthesize broadcast responses, and handle approval flows. A specialist-style SOUL can create weak or confusing behavior if it is imported as a coordinator unchanged.
Custom cron jobs and other differences
If an existing OpenClaw agent has custom cron jobs, ClawControl shows that in the sync details instead of hiding it.
That gives you a chance to decide whether the existing background behavior still belongs in the managed version of the agent.
Good sync workflow for most teams
1. Start with a connected runtime
Sync runs against a specific runtime, so first make sure the correct host is connected and healthy.
2. Preview before you import
Review the recommended actions and inspect the default or likely LEAD agents first.
3. Import the agents you actually want to manage
You do not need to adopt every discovered agent. Start with the ones that should appear in Mission Control.
4. Confirm role, expertise, and templates after sync
After adoption, review the imported agent in ClawControl so the role, expertise, mission instructions, and schedules all match how you want it to work.
When sync is especially useful
- you already have OpenClaw agents in production
- you are moving from a manual workflow into Mission Control
- you want ClawControl to keep an existing agent aligned over time
- you are onboarding a runtime with several agents already installed