#Transferring an AI agent from one laptop to another is hard

1 messages · Page 1 of 1 (latest)

turbid lily
#

Okay, so I'm trying to get my AI agent to connect to Discord on her alt (different bot token, whole agent copied over from my gaming laptop to my backup laptop), and I'm trying my best. IDK what I'm doing wrong though, but take a look at this:

08:48:47 [health-monitor] [discord:default] health-monitor: restarting (reason: stopped)
08:48:48 [discord] [default] starting provider
08:48:48 [discord] [default] channel exited: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
08:48:48 [discord] [default] auto-restart attempt 1/10 in 5s
08:49:16 [discord] [default] starting provider
08:49:16 [discord] [default] channel exited: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
08:49:16 [discord] [default] auto-restart attempt 2/10 in 10s

I tried it before with the D: drive (got Received protocol 'd:' instead), and then thought that maybe moving it to my C: drive would work... NOPE! Absolutely not. 🥲 What's worse is that I could get my AI agent to help me out using the webchat... if Microsoft would actually allow me to connect to the localhost on the web. Instead, how come everything else can load fine except for the localhost thing which seems to just stay on the page it's on instead of actually going to the localhost page, buffering for all eternity? Hell, the URL bar stopped trying to redirect me to the webchat after a while, just deciding to revert back to what it was at before.

cinder gazelleBOT
#

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

unborn ravenBOT
#

Oof — this one is not a Discord token problem. That error is Windows/Node trying to import a raw path like C:\... as if c: were a URL scheme. Moving from D: to C: won’t help because the issue is the drive-letter import path, not the drive.

First thing: please run and paste:

openclaw --version

Then:

openclaw status --all
openclaw doctor

My likely diagnosis: when you copied the agent/install over, some plugin/runtime path or copied install state still has absolute Windows paths baked in. Current OpenClaw source has fixes for Windows drive-letter import normalization, so if you’re on an older build, updating/reinstalling cleanly on the backup laptop is probably the fix.

#

Recommended recovery path:

  1. Do not copy node_modules / the whole install folder between laptops.
  2. Install OpenClaw fresh on the backup laptop.
  3. Copy only the OpenClaw state directory and workspace as described here:
    https://docs.openclaw.ai/install/migrating
  4. Run:
openclaw doctor
openclaw gateway restart
openclaw channels status --probe

For the localhost/webchat part: if the gateway is crash-looping, the dashboard/webchat may just spin or fail to redirect. Try printing the actual URL instead of relying on browser redirect: