Fix OpenClaw "Bundled Chrome Extension Is Missing"
A deep-dive on the OpenClaw error bundled Chrome extension is missing. Part of the OpenClaw troubleshooting hub.
Stuck on this? Get 1:1 OpenClaw help
Remote rescue for browser automation, extension, and Chrome tool problems. See the rescue session →
If OpenClaw reports that the bundled Chrome extension is missing, its browser tools can’t find the companion extension on disk. The fix is two commands and one manual load: run openclaw browser extension install, get the folder with openclaw browser extension path, then load that folder unpacked in chrome://extensions.
bundled Chrome extension is missing
Why OpenClaw needs a Chrome extension at all
OpenClaw’s browser automation tools drive a real Chrome session, reading pages, clicking, and filling forms. That control runs through a companion extension that OpenClaw ships alongside the CLI. If the extension files were never written to disk, or Chrome isn’t loading them, the browser tools have nothing to attach to and you get the “missing” error. This is not a corrupted install; the files just aren’t where Chrome is looking.
The fix
1. Install the extension files
# Write the bundled extension files to disk openclaw browser extension install
2. Get the folder path
# Print the path to the extension folder openclaw browser extension path
Copy the path it prints. That folder is what Chrome needs to load.
3. Load it unpacked in Chrome
- Open
chrome://extensions. - Toggle Developer mode on (top-right).
- Click Load unpacked.
- Select the folder from step 2.
The OpenClaw extension now appears in your extensions list, and the browser tools can attach to it. Re-run whatever browser command failed to confirm.
If it keeps disappearing
- Loaded from a temp folder. Unpacked extensions must live in a stable path. If
openclaw browser extension pathpoints into a temporary directory that gets cleaned, Chrome drops the extension on restart. Keep the files in a persistent location. - Developer mode got turned off. Chrome disables unpacked extensions when Developer mode is off. Leave it on.
- Files were removed. If the extension folder was deleted, re-run
openclaw browser extension installto rewrite it, then Load unpacked again. - Wrong Chrome profile. If you run multiple Chrome profiles, load the extension in the profile OpenClaw actually drives.
Quick reference
| Step | Command / action |
|---|---|
| Install files | openclaw browser extension install |
| Find the folder | openclaw browser extension path |
| Load it | chrome://extensions → Developer mode → Load unpacked |
Related OpenClaw guides
- Back to the full OpenClaw troubleshooting hub for all errors.
- See what the browser tools can do in the OpenClaw browser automation guide.
- Tools failing more broadly (NO_REPLY, “model is not allowed”)? See tools not working.
- On Windows and the CLI itself isn’t found? See openclaw not recognized on Windows.
Need help?
If Chrome still won’t load the extension after this, we offer a fixed-scope remote rescue session. See OpenClaw troubleshooting help →
Get guides like this in your inbox every Wednesday.
No spam. Unsubscribe anytime.
You'll probably need this again.
Press Cmd+D (Mac) or Ctrl+D (Windows) to bookmark this page.
Need OpenClaw fixed live?
Remote rescue sessions for gateway, auth, tunnel, VPS, and model access problems.
See Rescue Session