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

# Sign in

> Authorize the Droyd CLI through your browser and verify the session.

Sign in once from the CLI, approve the browser request, and return to the
terminal when the callback completes.

```bash theme={null}
droyd auth login
droyd auth status --json
```

The CLI keeps a refreshable user session outside your workspace and uses it for
normal research, wallet, and submission work. `droyd auth status` confirms the
current account without displaying credentials. Its access-token expiry is a
rotation timestamp, not the end of the stored login.

## Human access and automation

Use the browser sign-in flow for a person using the CLI. A Droyd API key is a
separate credential for an explicitly authorized CI or backend integration; it
is not a replacement for signing a person into a local workspace.

Run `droyd auth login` again only when status requires reauthentication or token
refresh fails. Never paste access tokens, refresh tokens, or API keys into a
prompt, command argument, or project file.