Skip to main content
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 and sign in with GitHub. A new human account starts with zero prepaid credit. Add credit before provisioning. To authorize the CLI:
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

Agent signup creates its own organization with trial credit. To see those existing machines from the dashboard, claim that organization. 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 and Agent authentication.