Skip to content
  • internal
  • ai
  • openclaw
  • operations
  • runbook

OpenClaw Operations Runbook (ConnectSoft)

This runbook covers day-2 operations for an OpenClaw installation running continuously on a remote Windows workstation.

Health and status

Use OpenClaw diagnostics first:

  • openclaw gateway status
  • openclaw status
  • openclaw health
  • openclaw doctor

Logs

Use:

  • openclaw logs

Note

Keep logs free of secrets. If you must debug an auth issue, rotate credentials afterward.

Configuration changes

  • Prefer the Control UI config form (when safe) for small edits.
  • For bulk changes, edit ~/.openclaw/openclaw.json directly.\n+ OpenClaw validates config strictly. If the gateway won’t start:\n\n- run openclaw doctor\n- revert the last change\n+

Upgrades

Recommended policy:

  • upgrade on a schedule (monthly)\n+- pin/record the installed OpenClaw version\n+- after upgrade: re-run openclaw doctor and smoke test an assistant\n+

Backup and restore (workstation)

Back up at least:

  • OpenClaw config file\n+- state directory (if you rely on persisted pairing/allowlists)\n+- C:\\OpenClaw\\workspaces\\connectsoft\\indexes\\ (optional; can be rebuilt)\n+

Troubleshooting checklist

  • Confirm Node and OpenClaw versions\n+- Confirm the gateway port (18789) is not blocked\n+- Confirm the service account has permission to read/write:\n+ - repos folder\n+ - runs folder\n+ - indexes folder\n+- Rebuild semantic index if retrieval quality degrades\n+