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

# bead dashboard login

> Complete bead dashboard login, authorize the CLI, and connect your agent organizations.

Complete bead dashboard login for human access and an agent credential for automated work. Both operate within an organization.

## Human sign-in

Open [app.bead.run](https://app.bead.run) and sign in with GitHub. A new human account starts with zero prepaid credit. [Add credit](https://docs.bead.run/platform/top-up.md) before provisioning.

To authorize the CLI:

```bash theme={null}
bead login
```

Open the printed verification link, sign in with GitHub, and approve the agent. The CLI saves the returned access token privately. Device authorization expires after ten minutes; restart login if it expires.

Device login grants `read write` access for one hour without admin scope; use the dashboard or an admin-scoped API key for ownership, membership, key creation, or billing administration. To renew expired access, select a fresh private `BEAD_API_KEY_FILE` and run `bead login` again; login does not overwrite an existing file.

## Agent organizations

```bash theme={null}
bead signup
```

Agent signup creates its own organization with [trial credit](https://docs.bead.run/platform/trial-credit.md). To see those existing machines from the dashboard, [claim that organization](https://docs.bead.run/organizations/ownership.md). A separate human signup does not automatically attach the agent's workspace.

## Reinstalling or using a second computer

Your resources belong to the organization. Installing the CLI does not copy credentials to the new computer. Use `bead login` for human authorization or securely provision an existing scoped API key.

Both signup and login refuse to overwrite an existing credential destination. Use the existing account, or select a fresh private `BEAD_API_KEY_FILE` for a deliberate account change.

## Account boundaries

API credentials carry organization authority. A delegated OAuth token inherits its credential's organization, scope, expiry, revocation, and prepaid budget constraints. Check the selected organization before creating paid work or changing membership.

Read [API keys and scopes](https://docs.bead.run/platform/api-keys.md) and [Agent authentication](https://docs.bead.run/platform/agent-auth.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.