This token can change which cloud account and which panel this process trusts, and it can install code into it. Keep it separate from PROVISIONER_TOKENS.
Held in this tab only. Closing it ends the session — nothing is stored on disk and no cookie is set.
Set here, a value lives in memory only and is gone on restart — that is the cost of never writing a credential to disk. Anything this process should come back up with belongs in its environment instead.
CLOUD_DRIVER picks one of these; a provider with names still missing cannot be used until they are set above. What each capability means is in docs/PROVIDER-CAPABILITIES.md; the vendors with no driver yet are in docs/PROVIDER-MATRIX.md.
A provider module runs with everything this process can reach — the environment, the network and both databases. There is no sandbox. Install one only if you would deploy it as part of the image, and read it first.
Written to the provider directory and loaded straight away — no restart. It has to export a provider object answering every capability; one that says it cannot do a required thing is refused and nothing is written. There is a working example in docs/AGENTS.md.