> ## Documentation Index
> Fetch the complete documentation index at: https://mulerun.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Doctor

> Print environment and configuration diagnostics

`mulerun doctor` is the first thing to run before opening a support
ticket. It prints:

* CLI version and distribution profile
* Resolved API base URL and proxy
* Login status (without revealing the token)
* Vendor-install paths for `code` and `studio` runtimes
* A handful of environment-sanity checks

```bash theme={null}
mulerun doctor
mulerun doctor -o json     # machine-readable
```

The command never sends user input over the network beyond the basic
"can I reach the API host?" probe, and it never prints secrets.

## When to run it

* After install — confirms the binary, runtimes, and login are all healthy.
* Before filing a bug — paste the output so we can see your build, OS,
  and resolved config without back-and-forth.
* After changing `MULERUN_BASE_URL` / `MULERUN_PROXY` — confirms the new
  value took effect.