#Doctor command

devboy doctor runs diagnostic checks for your local DevBoy setup and reports problems across config, credentials, provider APIs, MCP tools, and proxy servers.

#Quick start

# Run full diagnostics
devboy doctor

# List all available check IDs
devboy doctor --list-checks

# Run only selected checks
devboy doctor --checks config.exists,providers.github

# JSON output for scripts/CI
devboy doctor --format json

#CLI commands

#Run full diagnostics

devboy doctor

#List available checks

devboy doctor --list-checks

#Run selected checks

# Comma-delimited
devboy doctor --checks config.exists,config.valid_toml

# Repeated flag
devboy doctor --checks credentials.github --checks providers.github

#JSON output

# Full report in JSON
devboy doctor --format json

# JSON for selected checks
devboy doctor --format json --checks providers.github,providers.gitlab

#Options

#Exit codes

This makes devboy doctor safe to use in CI gates.

#Available checks

#Environment

• environment.os_support - Operating system supported
• environment.config_dir - Config directory exists
• environment.credential_store - Credential store available

#Configuration

• config.exists - Config file exists
• config.valid_toml - Config file valid TOML
• config.active_context - Active context valid

#Credentials

• credentials.github - GitHub token available
• credentials.gitlab - GitLab token available
• credentials.clickup - ClickUp token available
• credentials.jira - Jira token available

#Provider connectivity

• providers.github - GitHub API connectivity
• providers.gitlab - GitLab API connectivity
• providers.clickup - ClickUp API connectivity
• providers.jira - Jira API connectivity

#MCP and proxy

• mcp.tools - Built-in MCP tools configuration
• proxy.servers - Proxy MCP server connectivity

#Examples

# Check only config validity and active context
devboy doctor --checks config.valid_toml,config.active_context

# Check provider API access only
devboy doctor --checks providers.github,providers.gitlab

# Save JSON report
devboy doctor --format json > doctor-report.json

#Typical workflow

1. Run devboy doctor.
2. Fix reported errors first.
3. Re-run with targeted checks using --checks.
4. Add devboy doctor --format json in CI if you want automated validation.