Authdog CLI beta: identity navigation from your terminal
Install the Authdog CLI beta, sign in through your browser, inspect your identity, and choose an active environment without copying IDs.
Authdog Team
Authdog CLI 0.1.0-beta.1 brings identity exploration into a focused terminal interface. We built it for developers who need to understand their current identity context and move between organizations, tenants, projects, and environments, without repeatedly copying IDs out of a browser tab.
This first beta is deliberately interactive and read-only. It won't create users, rotate keys, or automate deployments. That's not what it's for yet.
Install the beta
On macOS or Linux:
curl https://cli.auth.dog/install -fsS | bashOn Windows PowerShell:
iwr -useb https://cli.auth.dog/install.ps1 | iexThe installer picks a release archive for your current operating system and architecture. If you need more control, set AUTHDOG_CLI_VERSION to pin a release, INSTALL_DIR to choose a destination, or AUTHDOG_CLI_USE_MUSL=1 on supported Linux musl builds.
Once it's installed, launch the fullscreen interface with authdog-cli.
Sign in and check who you are
Type /login inside the CLI. Authdog opens a browser for authentication, then hands control back to a one-time callback on your machine. Once that's redeemed, the CLI stores the resulting session locally and you're in.
From there, /whoami (or its /me alias) calls the authenticated /v1/userinfo endpoint. The Pretty view groups the useful fields into readable tables; the Raw view gives you indented JSON if you want to see exactly what came back.
Pick the context you need
The command palette gives you focused pickers for each level of the hierarchy:
/organizationsor/orgs/tenants/projects/browseor/navigator
/browse ties the whole thing together. Choose an organization, tenant, project, and environment, and the CLI keeps that as your active scope. Escape moves you back through earlier choices if you want to change your mind partway through.
/status shows you where the credential lives and what's currently selected. /logout removes the local credential file when you're done.
What the beta doesn't do yet
This release is optimized for interactive discovery, not automation. Output lives inside the terminal UI rather than acting as stable machine-readable stdout, resource actions are read-only, network requests are synchronous, and token refresh isn't exposed as a workflow yet.
Those limits are intentional for now. They keep the beta genuinely useful without pretending to offer management capabilities it doesn't have. The goal at this stage is simple: make your identity context easy to see, choose, and reason about.