OpenClawDocs
On this page

On this page

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this page

Gateway

Doctor

openclaw doctor is the repair and migration tool for OpenClaw. It fixes stale config/state, checks health, and provides actionable repair steps.

This page is an index. Doctor is documented on seven pages, one per reader job. Open the page that matches your task.

Database store diagnostics

Doctor reports configured and observed engines separately for each discovered physical store, including agent databases, Matrix roots, and fixed-local safety and credential stores. Absent optional stores are informational and do not require their plugin's database port API. Unknown schema, connectivity, ownership, or backup facts stay unknown with an actionable next step. Read the PostgreSQL Doctor guide for field definitions, output examples, and recovery instructions. For example, observed=sqlite (mismatch); schema=26, expected=26, pending=0 means the schema is current but the configured PostgreSQL engine has not been applied by a port. An older readable state or agent schema still reports its version and pending migrations when port validation refuses it. An inaccessible store remains in the report as unknown and names the permission repair; it is not reported as absent. JSON includes every inspected store in databaseStores, independent of the finding severity filter. Store findings also carry the same observations in details; inspecting them does not migrate data.

Doctor pages

Page Read it when
Run doctor Run the command, pick automation flags, and read the read-only lint report.
What doctor checks A summary of every repair, migration, and health check, grouped by area.
Config and migration repairs Checks 0-2: config normalization, the legacy config key table, and update-time schema publication.
Provider and route repairs Checks 2b-2g: provider overrides, browser and Chrome MCP readiness, OAuth TLS, and route cleanup.
State, session, and plugin repairs Checks 3-7b: disk layout, cron store, session integrity, model auth, sandbox, and plugin installs.
Gateway, service, and security checks Checks 8-17: service migrations, pairing, security warnings, workspace status, auth, health, and supervisors.
Workspace tips and Dreams UI actions Checks 18-20, plus the Control UI Dreams backfill, reset, and clear actions.

Where each section moved

Every section and check title from the previous single-page version keeps its anchor here, so an existing link such as /gateway/doctor#9-security-warnings still resolves. Each entry points at the page that now holds the content.

Was this useful?