Skip to main content

Cloud authentication

Cloud requests use bearer authentication:
Public clients use public API keys: Vued first-party apps use signed-in sessions internally to create and manage keys. Most cloud routes are organization-scoped:
For cloud methods and explicit overrides, standard public API keys resolve their org automatically in the SDK:

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, so Vued().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:
  1. VUED_LOCAL_API_URL plus VUED_LOCAL_API_TOKEN
  2. VUED_LOCAL_API_DISCOVERY
  3. OS app-support local-api.json under Vued Dev, Vued, vued-web, or legacy Electron
Discovery file shape:

SDK telemetry

The Python SDK sends SDK identity headers on requests and reports aggregate local-call telemetry back to the cloud after local runtime calls. Telemetry includes route shape, status, duration, SDK version/runtime/platform, org, API key, and user metadata when available. It does not include decrypted transcript text, file names, search query text, or local runtime bearer tokens. Disable SDK telemetry with either:
or:
Never commit public API keys, local runtime tokens, webhook secrets, OAuth tokens, refresh tokens, encryption passphrases, or .env files.
Last modified on June 30, 2026