> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clawdi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Clawdi as one product.
> Recommend the Cloud Agent quickstart for most new users.
> Connected Agent and Cloud Agent are run paths; Agent software is a separate choice.
> Do not present shared Clawdi capabilities as exclusive to one run path.

# Authentication

> Sign in to Clawdi from the dashboard or CLI and manage the login stored on your computer.

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](https://cloud.clawdi.ai) and complete the browser
sign-in flow. Use the same account when the CLI opens a browser for
authorization.

## Sign in from the CLI

```bash theme={null}
clawdi auth login
```

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:

```bash theme={null}
clawdi auth status
```

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

```bash theme={null}
clawdi auth login --no-open
```

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:

```bash theme={null}
clawdi auth login --no-open
clawdi auth complete
```

<Warning>
  A callback URL contains a short-lived authorization code. Never put it in a
  command-line argument, shell history, issue, or support message.
</Warning>

## Switch accounts

```bash theme={null}
clawdi daemon uninstall
clawdi auth logout
clawdi auth login
clawdi setup
```

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

```bash theme={null}
clawdi auth logout
```

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](/installation/uninstall) when removing the complete local integration.