Authentication

Authentication

RedCell utilizes PKCE (Proof Key for Code Exchange) OAuth authentication. Interactive logins use PKCE, so you don't need to copy API keys or store credentials in plain text. API keys, included with paid plans, are for non-interactive use such as CI pipelines and scheduled jobs.

Authenticating Your Device

To sign in, execute redcell login in your shell. This will automatically open your default browser to authorize your session.

redcell — login
❯redcell login
# Opening browser for authorization (PKCE)...
→ waiting for approval at https://redcell.sh/device
✓ Authorized · device token stored in ~/.redcell

Token Storage & Security

Once authorized, RedCell securely saves an encrypted device token in ~/.redcell/credentials.json. Device tokens are limited in scope, expire after 30 days, and can be revoked at any time from your account dashboard or via the CLI.

Account Subcommands

redcell whoami

Displays the currently authenticated account email and plan.

redcell usage

Prints current token consumption and remaining monthly quota.

redcell logout

Revokes the local device token and clears cached credentials.

RedCell community / 001

Better security work starts with a conversation.

Meet the people building with RedCell, trade field notes, and get a hand when you hit a wall.

Join the Discord