Cloud authentication
Cloud requests use bearer authentication:
Vued first-party apps use signed-in sessions internally to create and manage keys.
Most cloud routes are organization-scoped:
Public API key scopes
Local runtime authentication
Vued Desktop and Vued headless both write a local discovery file that contains the local API URL and a runtime bearer token. They also create and store a scoped local SDK key for decrypted local reads. The Python SDK reads discovery automatically, soVued().search(...) works after either Desktop or headless setup.
Headless setup signs in through https://vued.ai/cli-auth, stores a refresh token securely when available, and asks for the Vued encryption passphrase so encrypted sync can decrypt locally. The daemon refreshes expired Vued sessions automatically on cloud 401. If refresh requires user action, vued status, vued doctor, and SDK local errors surface an auth-required state and the user should run vued setup --reset.
Discovery order:
VUED_LOCAL_API_URLplusVUED_LOCAL_API_TOKENVUED_LOCAL_API_DISCOVERY- OS app-support
local-api.jsonunderVued Dev,Vued,vued-web, or legacyElectron