OpenClaw Update Broke My Config (Quick Fix)

Just ran into this after updating OpenClaw and figured I’d save you the headache.

What happened:

After the update, OpenClaw started failing with:

Invalid config...

plugin path not found: /home/claw/.npm-global/lib/node_modules/openclaw/extensions/acpx

At first glance it looks like your config is corrupted.

It’s not.

The update changed where extensions live.

Old path:

.../openclaw/extensions/acpx

New path:

.../openclaw/dist/extensions/acpx

So your config is still pointing to a directory that literally doesn’t exist anymore.

How I diagnosed it:

Ran:

find /home/claw -type d -name acpx 2>/dev/null

Saw that ACPX still existed, just in a different location (dist/extensions).

Fix (30 seconds):

sed -i 's|/openclaw/extensions/acpx|/openclaw/dist/extensions/acpx|g' ~/.openclaw/openclaw.json

Then:

openclaw gateway status

Back to normal.

Takeaway:

If OpenClaw suddenly says your config is invalid after an update, don’t panic.

It’s probably not your JSON.

It’s almost always:

stale plugin paths

moved extensions

or renamed directories

Check the actual filesystem before you start rewriting configs.

If you’re building on top of OpenClaw, expect this kind of breakage.

Pin paths or make them dynamic, otherwise updates will quietly brick your setup.

0 comments

skool.com/the-openclaw-expedition-1568

A paid OpenClaw community to learn and keep up with this bleeding edge AI assistant technology.