Skip to content
ginko

Authentication

Authentication is optional. ginko works fully offline for session management, planning, and local event logging. Cloud authentication unlocks:

  • Knowledge graph (semantic search, document connections)
  • Team collaboration (invitations, task assignment)
  • Web dashboard
  • Cross-device session sync

Login with GitHub

Section titled “Login with GitHub”
Terminal window
ginko login

This opens your browser for GitHub OAuth authentication via Supabase. After authorizing, you’re redirected back and the CLI stores your session locally.

Verify authentication

Section titled “Verify authentication”
Terminal window
ginko whoami

Shows your authenticated identity:

Authenticated as: chris@watchhill.ai
GitHub: @ginko-chris
Team: WatchHill AI

Force re-authentication

Section titled “Force re-authentication”
Terminal window
ginko login --force

Logout

Section titled “Logout”
Terminal window
ginko logout

Clears your local authentication session. Local ginko features continue to work.

Token storage

Section titled “Token storage”

Authentication tokens are stored in ~/.ginko/auth.json (your home directory, not the project). This file is automatically added to .gitignore patterns.