Cloudflare Workers / stack diagnostics
See every binding.
Then press run.
Workers Doctor resolves your selected environment, maps the Worker graph, and shows exactly which resources stay local or reach Cloudflare.
- 00
- credentials
- 03
- config formats
- 09
- diagnostics
01 / EFFECTIVE STATE
A Wrangler file is not the stack that runs.
Named environments replace non-inherited bindings. Remote flags move individual resources back to Cloudflare. Service names change across environments. Workers Doctor computes the result before a development process touches anything.
02 / INSPECTION
One plan for the whole repository.
Scan JSONC, JSON, or TOML. Keep the readable report in the terminal, emit JSON for tooling, Graphviz for architecture, or annotations for CI.
$ workers-doctor inspect -e staging
2 workers · 3 bindings · 1 remote
api-staging
service AUTH → auth-staging local
d1 DB → preview-db remote
auth-staging
kv SESSIONS local
i WD002 Remote bindings will be used
03 / GUARDED START
The command is visible before the process begins.
- 01
Discover
Find every Worker without walking generated directories.
- 02
Resolve
Apply the selected environment and classify each binding.
- 03
Verify
Stop on missing environments, duplicate bindings, and service graph errors.
- 04
Start
Launch dependencies first on predictable local ports.
Open source / deterministic / offline inspection