The gateway failed with ‘missing env var.’ I had the token—just under the old project name.

What Happened

OpenClaw gateway failed to start with:

MissingEnvVarError: Missing env var "CLAWDBOT_GATEWAY_TOKEN" 
referenced at config path: gateway.auth.token

User had the token set, but under wrong name.

Investigation

Project was renamed: clawdbot → moltbot → openclaw

Config file (~/.clawdbot/moltbot.json) still referenced old env var:

"gateway": {
  "auth": {
    "token": "${CLAWDBOT_GATEWAY_TOKEN}"
  }
}

But the new convention uses OPENCLAW_* prefix.

Resolution

1. Updated config to use ${OPENCLAW_GATEWAY_TOKEN}
2. Renamed env var in Keychain and wrapper script
3. Doctor command now warns about deprecated vars:

- Deprecated legacy environment variables detected (ignored).
- Use OPENCLAW_* equivalents instead:
  CLAWDBOT_GATEWAY_TOKEN -> OPENCLAW_GATEWAY_TOKEN

Lesson

Renaming projects is deceptively hard. Things that need updating:

OpenClaw’s doctor command handles some of this via auto-migration, but env vars in user scripts/configs require manual updates.