Authdog CLI beta: identity navigation from your terminal

Authdog CLI 0.1.0-beta.1 brings identity exploration into a focused terminal interface. It is built for developers who need to understand their current identity context and move between organizations, tenants, projects, and environments without repeatedly copying identifiers from a browser.

This first beta is intentionally interactive and read-only. It does not create users, rotate keys, or automate deployments.

Install the beta

On macOS or Linux:

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

On Windows PowerShell:

iwr -useb https://cli.auth.dog/install.ps1 | iex

The installer selects a release archive for the current operating system and architecture. Set AUTHDOG_CLI_VERSION to pin a release, INSTALL_DIR to choose a destination, or AUTHDOG_CLI_USE_MUSL=1 for supported Linux musl builds.

Launch the fullscreen interface with authdog-cli.

Sign in and inspect your identity

Enter /login inside the CLI. Authdog opens a browser for authentication, then returns control to a one-time callback on your machine. After redemption, the CLI stores the resulting session locally.

Use /whoami or its /me alias to request the authenticated /v1/userinfo response. The Pretty view groups useful fields into readable tables. The Raw view exposes indented JSON for inspection inside the interface.

Pick the context you need

The command palette exposes focused resource pickers:

• /organizations or /orgs
• /tenants
• /projects
• /browse or /navigator

/browse connects the complete flow. Choose an organization, tenant, project, and environment, then keep that scope as your active context. Press Escape to move back through earlier choices.

Use /status to inspect credential location and selected scope. Use /logout to remove the local credential file.

Beta boundaries

This release optimizes for interactive discovery. Output stays inside the terminal UI rather than acting as stable machine-readable stdout. Resource actions are read-only, network requests are synchronous, and token refresh is not yet exposed as a workflow.

Those boundaries matter. They keep the beta useful without implying automation or management capabilities it does not ship. The current goal: make identity context easy to see, choose, and reason about.