Technical reference for the OpenClaw framework. Real-time synchronization with the official documentation engine.
Use this file to discover all available pages before exploring further.
Doctor
text
openclaw doctor
is the repair + migration tool for OpenClaw. It fixes stale config/state, checks health, and provides actionable repair steps.
Quick start
bash
openclaw doctor
Headless and automation modes
```bash}
openclaw doctor --yes
```
text
Accept defaults without prompting (including restart/service/sandbox repair steps when applicable).
```bash}
openclaw doctor --repair
```
text
Apply recommended repairs without prompting (repairs + restarts where safe).
```bash}
openclaw doctor --repair --force
```
text
Apply aggressive repairs too (overwrites custom supervisor configs).
```bash}
openclaw doctor --non-interactive
```
text
Run without prompts and only apply safe migrations (config normalization + on-disk state moves). Skips restart/service/sandbox actions that require human confirmation. Legacy state migrations run automatically when detected.
```bash}
openclaw doctor --deep
```
text
Scan system services for extra gateway installs (launchd/systemd/schtasks).
If you want to review changes before writing, open the config file first:
bash
cat ~/.openclaw/openclaw.json
What it does (summary)
Dreams UI backfill and reset
The Control UI Dreams scene includes Backfill, Reset, and Clear Grounded actions for the grounded dreaming workflow. These actions use gateway doctor-style RPC methods, but they are not part of
text
openclaw doctor
CLI repair/migration.
What they do:
Backfill scans historical
text
memory/YYYY-MM-DD.md
files in the active workspace, runs the grounded REM diary pass, and writes reversible backfill entries into
text
DREAMS.md
.
Reset removes only those marked backfill diary entries from
text
DREAMS.md
.
Clear Grounded removes only staged grounded-only short-term entries that came from historical replay and have not accumulated live recall or daily support yet.
What they do not do by themselves:
they do not edit
text
MEMORY.md
they do not run full doctor migrations
they do not automatically stage grounded candidates into the live short-term promotion store unless you explicitly run the staged CLI path first
If you want grounded historical replay to influence the normal deep promotion lane, use the CLI flow instead: