Your Clawdi account is shared across the dashboard, Connected Agents, and
Cloud Agents. Signing in does not change where an Agent runs or which Agent
software it uses.
Sign in from the dashboard
Open the Clawdi dashboard and complete the browser
sign-in flow. Use the same account when the CLI opens a browser for
authorization.
Sign in from the CLI
The CLI uses the OAuth device authorization grant. It prints a sign-in link
and a short code, and opens a browser in a local interactive terminal. Open
the link, sign in, check that the page shows the same code, and approve. The
CLI finishes automatically and stores the login under ~/.clawdi/auth.json
by default. Treat that file as a credential: do not copy it into a repository,
support ticket, or chat.
For clawdi.ai, the verification page is
accounts.clawdi.ai/device. The code expires
after 10 minutes. Approve only a sign-in you started yourself.
Check the active credential source without printing the token:
The output can still contain your email address, user ID, local paths, and API
origin. Redact those fields before posting it publicly.
CLI permissions
Starting in CLI 0.15.7, signing in with clawdi auth login gives the CLI
the same access as the dashboard, with these exceptions:
- Cloud: review or revoke API keys and approve device sign-ins in the
browser.
- Hosted billing: enter payment methods, enable automatic Wallet reload,
and change plans in the browser.
clawdi wallet portal prints the billing
URL.
New API keys can no longer be created. The dashboard lists existing keys with
their permissions and expiry so you can revoke them. Existing API keys retain
their limited permissions. Signing in with an API key through --manual does
not grant the access provided by browser sign-in.
CLI versions before 0.15.0 can no longer complete sign-in. Update the
CLI before running clawdi auth login.
Sign in over SSH or without a browser
Open the printed link on any device with a browser, confirm the code matches
the terminal, and approve. Keep the command running; it finishes automatically
after approval. Use --no-open to skip opening a browser automatically.
If the command was interrupted, resume waiting for the same sign-in:
If the code expired or you denied the request, run clawdi auth login again
for a new code.
Self-hosted
For self-hosted Clawdi using Clerk OAuth, follow
Clerk’s OAuth application settings guide:
in the Clerk Dashboard, open OAuth applications, select the CLI’s OAuth
application, and enable Device authorization grant. Through the
Clerk Backend API,
set device_authorization_grant_enabled to true on that application.
If the grant is disabled, the CLI reports that the server’s sign-in app does
not allow device sign-in and asks an administrator to enable it. As a fallback,
sign in with an existing API key in an interactive terminal:
This accepts an existing key; it does not create a new one.
Switch accounts
Stop the daemon first so it does not continue using the previous login. After
signing in again, run setup to refresh the Connected Agent registration and
background service.
Sign out
Sign-out removes persisted credentials and cached environments on this
computer and attempts to revoke the remote OAuth grant. It does not delete the
account or its server-side data. See Uninstall the Clawdi
CLI when removing the complete local integration. Last modified on October 7, 2026
