Troubleshooting

Doctor reports backend unreachable

• Verify the --backend-url is correct and reachable from your OpenClaw host.
• Check that the backend is actually running (self-hosted) or that the hosted service is not under maintenance.
• Ensure there are no proxy or firewall rules blocking the connection.

Doctor says capture-only is not ready

• The backend may be reachable but missing required auth configuration.
• Verify your AM_SERVER_API_KEYS on the backend includes the key you are passing.
• Check backend logs for OpenClaw pipeline initialization errors.

Doctor says augment-context is not ready

• The context engine pipeline may not be healthy. Check /health/onboarding for the exact flag.
• Verify that embedding providers and Neo4j are reachable from the backend.
• If you do not need prompt augmentation, run setup with --mode capture_only.

Setup succeeds but project status fails

• Confirm the saved config has the correct backendUrl and apiKey.
• Check that the workspace/agent identity resolved by the backend matches what you expect.
• Try initializing a project explicitly: openclaw agentic-memory project init my-project.

Empty memory search results

• Ensure a project is active: openclaw agentic-memory project status.
• Verify that turns are actually being ingested (check backend metrics or logs).
• If using a self-hosted backend, confirm Neo4j has data for the resolved workspace.

Quick diagnostic checklist

openclaw agentic-memory doctor curl -H "Authorization: Bearer YOUR_KEY" \ BACKEND_URL/openclaw/health/detailed curl -H "Authorization: Bearer YOUR_KEY" \ BACKEND_URL/metrics openclaw agentic-memory project status