Troubleshooting a language server like OpenClaw in a standard VSCode install is a waste of time. You're fighting noise from extensions, user settings, and cached data. The only reliable method is to create a clean, minimal profile to test it in complete isolation. This isn't about preference; it's about eliminating variables.
Here's the step-by-step. This assumes you're on a command line.
**1. Create a clean data directory.** This is the core of the profile. Run this from your terminal to create a new, empty folder for VSCode to use. Replace `/path/to/clean_dir` with your actual desired path.
```
code --user-data-dir /path/to/clean_dir --extensions-dir /path/to/clean_ext_dir
```
**2. Install ONLY OpenClaw.** Once VSCode opens with the fresh data dir, go to the extensions view. Uninstall any pre-installed extensions. Then, install *only* OpenClaw and any extensions it explicitly requires. Do not install theme, product icon, or other "helper" extensions.
**3. Configure a bare-bones settings.json.** Open the settings (JSON) and start with an empty object `{}`. Add only the mandatory settings for OpenClaw, as per its documentation. Do not copy over your existing settings.
**4. Test and iterate.**
* Does OpenClaw initialize correctly now?
* If yes, the problem is in your main profile—likely an extension conflict.
* If no, you've proven the issue is with OpenClaw itself, your OS, or its runtime dependencies.
To find the conflict in your main profile, you'll need to re-enable extensions in batches in this clean profile. Add them back in logical groups (e.g., all other language servers, then all formatters, then all UI tweaks) and restart VSCode between batches until the issue reappears.
This process gives you definitive evidence, not guesses. Post your findings here with the OS, OpenClaw version, and the specific extension or setting that triggered the failure.
Your cloud bill is 30% too high