GitHub subject
The immutable GitHub user ID, handle, and avatar identify the operator. The raw GitHub token is checked once and never stored.
carries: verified identityIdentity control room
Sign in with GitHub. Keep your usage history.
Start a browser session for site controls or verify the GitHub CLI already authenticated on your machine. Both resolve to one GitHub identity, not a full C0VIBE account, and neither path moves usage.
browser sessionCLI identityno WorkOS gatelinked history
identity@vibeusageZERO USAGE MOVEMENT
+--------------------------------------------------+ | VTRK://GITHUB-PROOF//ADAPTIVE-ACCOUNT | |--------------------------------------------------| | github id immutable identity anchor | | auth channel browser session or existing CLI | | blue check identity only, NOT usage truth | | cli history linked after identity proof | +--------------------------------------------------+
Live identity state
GitHub sign-in console
checking GitHubno browser session
Choose where GitHub should sign you in.
The browser creates a site session. The CLI verifies this machine. Both attach to the same immutable GitHub identity.
Browser sessionsite controls+CLI identityexisting history->GitHub subjectone profile
Browser sign-in gives this site a session. CLI verification gives this machine a keyring token. The raw GitHub token is used once and is never persisted by VibeTRACKER.session@githubSITE SESSION
One browser sign-in. Four inspectable steps.
- 01GitHub consentYou authenticate on github.com, never in a copied terminal command.
- 02Server callbackVibeUsage exchanges the one-time authorization code server-side.
- 03Account sessionSupabase stores the browser session in secure cookies.
- 04Identity linkYour immutable GitHub user ID anchors existing and future usage.
GitHub is the identity anchor.OAuth and GitHub CLI proof resolve to the same immutable subject. Existing submissions attach without changing usage evidence.inspect proof labels
CLI keyring
VibeTRACKER issues its own revocable token after proof. The token stays in the OS keyring; the GitHub credential does not move with it.
carries: CLI ownershipUsage ledger
Historical submissions keep the same identity ID. Linking attaches ownership without rewriting totals, trust labels, or rank evidence.
carries: existing historyC0VIBE settings
A ten-minute one-time claim gives WorkOS a stable identity anchor. Provider credentials remain local and are never copied into settings.
carries: identity reference- raw GitHub tokens
- 0 stored
- hidden usage moves
- 0
- profile forks
- 0
- migration claim
- 10 min