Authentication
Use the CLI to authenticate with the Dreadnode platform and manage provider API keys for local agent runs. You can log in before launching the TUI or from inside the client itself.
Login methods
Section titled “Login methods”Use dreadnode login for a saved platform profile, or /login from inside an interactive session.
You can authenticate with a browser-based device flow or by pasting an API key:
dreadnode logindreadnode login <api-key>/loginUse --server <url> to target a self-hosted platform instance:
dreadnode login --server http://localhost:3000/login --server http://localhost:3000User API keys
Section titled “User API keys”You can manage multiple API keys for a single account via the REST API:
GET /api/v1/user/api-keys— list active keysPOST /api/v1/user/api-keys— create a new key (optionalname)DELETE /api/v1/user/api-keys/{key_id}— revoke a key
Provider API keys
Section titled “Provider API keys”Use the /keys command to store provider keys used by generators.
/keys set <provider> <key>Supported providers: anthropic, openai, google, mistral, groq, custom.
| Provider | Key format (example) |
|---|---|
| anthropic | sk-ant-... |
| openai | sk-... |
AIza... | |
| mistral | mistral-... |
| groq | gsk_... |
| custom | custom-... |
Profiles
Section titled “Profiles”Profiles store saved platform credentials under ~/.dreadnode and the most recent login becomes active.
To switch profiles, log in to another server or set the profile explicitly via the DREADNODE_PROFILE environment variable:
DREADNODE_PROFILE=dev.app.dreadnode.io dreadnodeConnect to a Dreadnode server
Section titled “Connect to a Dreadnode server”If you are using a self-hosted deployment, connect your CLI session to the server URL:
/connect <url>