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 starts an OAuth authorization-code flow with PKCE and opens the
authorization URL in your browser. After approval, it 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.
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.
Sign in over SSH or without a browser
Open the printed URL on a computer with a browser. If the browser cannot reach
the remote loopback callback, paste the complete failed callback URL into the
CLI’s masked prompt.
For a non-interactive terminal, start the same flow and complete it later by
providing the callback URL on standard input:
A callback URL contains a short-lived authorization code. Never put it in a
command-line argument, shell history, issue, or support message.
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.