Auth
ClawHub uses GitHub for web sign-in. The CLI uses ClawHub API tokens created through that signed-in account.Web sign-in
Use GitHub to sign in at clawhub.ai. Deleted, banned, or disabled accounts cannot complete normal ClawHub sign-in. If sign-in returns you to a logged-out state, your account may not be in good standing. If your account was banned or disabled, use the ClawHub appeal form if you believe this is a mistake.CLI login
The default CLI login uses device-code approval:- The CLI prints a one-time code and verification URL.
- Open the printed URL on this or another device and sign in with GitHub if needed.
- Confirm the code matches your terminal, then select Authorize.
- The CLI polls for approval, receives an API token, verifies it via
whoami, and stores it in your ClawHub config file.
clawhub login again if yours expires.
Headless login
Create a token in ClawHub Settings → API tokens, then pass it to the CLI:--no-input alone
still waits for device approval.
The default device flow also works from remote shells. --device explicitly
selects the same flow:
Token storage
Default config paths:- macOS:
~/Library/Application Support/clawhub/config.json - Linux/XDG:
$XDG_CONFIG_HOME/clawhub/config.jsonor~/.config/clawhub/config.json - Windows:
%APPDATA%\\clawhub\\config.json
Revocation
You can revoke API tokens in the ClawHub web UI. Revoked, invalid, or missing tokens return401 Unauthorized. Sign in again
with clawhub login or provide a fresh token with clawhub login --token.
Deleted, banned, or disabled accounts cannot continue using existing API tokens.
If your account was banned or disabled, use the
ClawHub appeal form if you believe this is a
mistake.