Depot env vars: DEPOT_TOKEN read order and DEPOT_ORG_ID
Shows how to fix depot env vars: DEPOT_TOKEN read order and DEPOT_ORG_ID. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Set them once and stop debugging auth. DEPOTORGID is the org ID: cache integrations use it as org context, and Depot CI and runners set it automatically.
Steps
- [Depot docs]: DEPOTTOKEN is the Depot auth token; the CLI reads explicit --token flags first, then DEPOTTOKEN, then locally stored login credentials. DEPOTCACHETOKEN is the short-lived cache token Depot injects automatically in Depot CI and GitHub Actions runner jobs; the CLI also reads it as a fallback. DEPOTORGID is the org ID: cache integrations use it as org context, and Depot CI and runners set it automatically. In Depot CI you do not need to set any of these yourself.
When to use
You are seeing this: [Depot docs]: DEPOTTOKEN is the Depot auth token; the CLI reads explicit --token flags first, then DEPOTTOKEN, then locally stored login credentials. Use this skill when you run into "Depot env vars: DEPOTTOKEN read order and DEPOTORG_ID".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.