Environment error? Paste it here
Copy the failing command and error output, or drop in a screenshot. EnvDoctor finds the cause and gives you repair steps you can copy and paste.
EnvDoctor
Get a fix in three steps
The next step from EnvDoctor
Copy it into your terminal to verify
Covers common dev tools
Turn the error into the next step
No cleanup, no explaining what the issue might be. Paste the error and get repair steps.
No cleanup needed
No need to organize your thoughts or explain what the issue might be. Just drop in the error and command.
It will not touch your config
When more info is needed, EnvDoctor only asks for read-only commands, like checking versions or DNS. It will not modify your config files.
Guidance you can follow
Each diagnosis explains what likely broke, why it happened, what to check next, and how to verify the result. Copy and paste ready.
EnvDoctor session
Claude Code + OpenClaw
Symptom
Claude Code loops after OpenClaw starts a repo task.
Likely cause
OpenClaw's filesystem MCP exits before handshake.
Repair step
Pin the Node path in the OpenClaw MCP command.
Verify
Run openclaw doctor, then retry claude --continue.
Rollback
Restore the timestamped openclaw.json backup.
$ claude --continue
It has seen common errors
Dependencies fail to install, dev servers will not start, builds break, deploys error out. Start debugging here.
Screenshots are fine
If the error is stuck in an image, upload the screenshot and EnvDoctor continues from the extracted text.
No useless questions
No wall of forms. EnvDoctor only asks one or two follow-up questions when they actually matter.
Helps locate where it broke
Your system info and command output help tell whether the issue is local config or the deployment platform.
Past sessions stay searchable
After signing in, every diagnosis is saved so you can track similar issues and compare before and after.
ENVDOCTOR