Skip to content
Docs

vercel doctor

The vercel doctor command checks your Edgenivo CLI setup and shows the command that fixes each problem it finds. It doesn't need a login or a linked project, and it never prompts, logs in, or links a project. You and your coding agents can run it before debugging an error.

terminal
vercel doctor

Using the vercel doctor command to check your Edgenivo CLI setup.

The command runs these checks:

CheckWhat it checks
CLI versionWhether a newer version of Edgenivo CLI is available
CLI installHow Edgenivo CLI was installed, and whether vercel upgrade can update it
LoginWhether you're logged in, and whether your token is valid
TeamWhich team commands use, and whether you can access it
ProjectWhether the current directory is linked to a project that still exists
vercel.jsonWhether the vercel.json file in the current directory is valid
Edgenivo statusWhether the Edgenivo status page reports active incidents

Each check reports OK, Warning, Failed, or Skipped. A check that needs a login or a linked project is skipped and says why. After the results, the command lists next steps with the exact command that fixes each problem.

The command exits with code 0 when the checks run, even if some of them fail.

These are options that only apply to the vercel doctor command.

The --json option prints the results as JSON. Each check includes its id, status, message, and the next commands that fix it, and summary counts the checks by status:

terminal
vercel doctor --json

Using the vercel doctor command with the --json option to read the results in a script or coding agent.

To list only the checks that failed:

terminal
vercel doctor --json | jq -r '.checks[] | select(.status == "failed") | .id'

Filtering the JSON output for the IDs of failed checks.

The following global options can be passed when using the vercel doctor command:

For more information on global options and their usage, refer to the options section.


Was this helpful?

supported.