CLI beta

Explore your identity stack from your terminal

Sign in through your browser, inspect your Authdog identity, and move through organizations, tenants, projects, and environments without losing context. Automation foundations are coming next.

1curl https://cli.auth.dog/install -fsS | bash

Today and next

Built for exploration, growing toward automation

Start with secure interactive navigation. Follow a clear roadmap toward predictable scripts, agents, and local developer workflows.

Available

Secure browser login

Authenticate in your browser, then return to the CLI through a short-lived, one-time local callback.

Available

Identity inspection

Check the active account and session context with /whoami before working in a workspace.

Available

Hierarchy navigation

Move through organizations, tenants, projects, and environments while keeping parent scope intact.

Available

Interactive browser

Explore identity resources in a focused terminal interface without memorizing every identifier.

Planned

Agent-safe automation

Planned non-interactive mode with stable JSON results, structured errors, and no hidden browser prompts.

Planned

Project linking

Planned Git-aware profiles that connect a checkout to its tenant, project, and environment context.

Planned

CLI doctor

Planned diagnostics for authentication, workspace links, API access, local configuration, and SDK setup.

Planned

Credential hardening

Planned OS keychain storage, safe file fallback, and automatic access-token refresh.

CLI workflows

Know where you are before you act

Current beta focuses on secure sign-in, identity inspection, and guided navigation. Automation follows with explicit, machine-readable behavior.

  • Authenticate through a short-lived browser flow
  • Confirm server-provided identity with /whoami
  • Keep tenant, project, and environment scope visible
  • Explore resources without copying identifiers between pages
# Launch the interactive CLI
$ authdog-cli

# Sign in through the browser
/login

# Inspect the authenticated identity
/whoami

# Verify credentials and active scope
/status

Why use the beta

Identity context without dashboard hopping

Keep account details and workspace scope close to the code you are already working on.

1

See your active identity

Ask the API who you are, inspect readable account details, and verify local session state.

2

Keep resource scope clear

Select a tenant, project, and environment while the CLI maintains their parent-child relationship.

3

Move without dashboard hopping

Browse the identity hierarchy from the same terminal where you build, test, and debug.

Explore Authdog from your terminal

Install the beta, sign in securely through your browser, and navigate your identity workspace without leaving the command line.