#Constant "Doctor" fixes since GPT 5.4 update

1 messages · Page 1 of 1 (latest)

clear etherBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

vague nimbusBOT
#

That line is coming from openclaw doctor auditing your macOS LaunchAgent (the background Gateway service), and it’s basically saying:

  • Your Gateway daemon is currently running with a Node binary inside nvm (e.g. ~/.nvm/versions/node/v22.22.0/bin/node)
  • That’s fine today, but it’s fragile: if you nvm install, nvm uninstall, upgrade nvm, or otherwise reshuffle versions, the daemon can end up pointing at a Node path that no longer exists (or is no longer the one you expect). Then you get “gateway weirdness” and Doctor keeps offering to repair things.

So it’s not a “GPT-5.4” problem per se — it’s a service-runtime stability warning.

The “make it stop” fix (recommended)

Use a “system” Node for the daemon (Homebrew Node), then let Doctor re-write the service to use it:

  1. Install Node via Homebrew (Node 22+):
  1. Re-sync the daemon definition:
openclaw gateway install --force
# 
openclaw gateway restart

(Doctor will also offer to do basically this interactively.)

This also fixes a related common issue Doctor warns about: service token drift (config token != plist env token), which can make the dashboard randomly go “unauthorized” after restarts.

If you want to stay on nvm anyway

You can, just treat it as “pinned” for the daemon:

  • don’t uninstall that exact Node version the LaunchAgent points at
  • whenever you update OpenClaw / change Node versions, re-run:
    openclaw gateway install --force then openclaw gateway restart

To pinpoint why you’re needing Doctor so often

Paste these (they’re the fastest signal):