Build, manage and test your Auth0 integrations from the command line.

auth0 test login.auth0 logs tail command.Install via Homebrew:
brew tap auth0/auth0-cli && brew install auth0
Install via cURL:
./auth0:
bash
curl -sSfL https://raw.githubusercontent.com/auth0/auth0-cli/main/install.sh | sh -s -- -b .bash
sudo mv ./auth0 /usr/local/bin[!TIP] On macOS, depending on the state of your current development environment you may have to first create the directory with
sudo mkdir -p /usr/local/binin order for the above command to work. Alternatively, you can move it to a directory of your choice and then add that directory to your $PATH instead.
Install via Scoop:
scoop bucket add auth0 https://github.com/auth0/scoop-auth0-cli.git
scoop install auth0
Install via Powershell:
powershell
$latestRelease = Invoke-RestMethod -Uri "https://api.github.com/repos/auth0/auth0-cli/releases/latest"
$latestVersion = $latestRelease.tag_name
$version = $latestVersion -replace "^v"powershell
Invoke-WebRequest -Uri "https://github.com/auth0/auth0-cli/releases/download/${latestVersion}/auth0-cli_${version}_Windows_x86_64.zip" -OutFile ".\auth0.zip"
Expand-Archive ".\auth0.zip" .\powershell
Alternatively, follow the instructions in the Manual section below. Learn more about environment variables in PowershellInstall via Go:
# Make sure your $GOPATH/bin is exported on your $PATH
# to be able to run the binary from any directory.
go install github.com/auth0/auth0-cli/cmd/auth0@latest
$ tar -xf auth0-cli_{version}_Darwin_{architecture}.tar.gz$ tar -xf auth0-cli_{version}_Linux_{architecture}.tar.gzauth0-cli_{version}_Windows_{architecture}.zip using your preferred method for working with compressed files.PATH and HOME environment variables include the folder where the binary was extracted.macOS/Linux:
PATH and HOME are set correctly:bash
export PATH=$PATH:/path/to/extracted/auth0/cli/folder
export HOME=/path/to/home/directory
Windows:
Run auth0
[!TIP] Autocompletion instructions for supported platforms available by running
auth0 completion -h
Authenticating to your Auth0 tenant is required for most functions of the CLI. It can be initiated by running:
auth0 login
There are two ways to authenticate:
Warning Authenticating as a user is not supported for private cloud tenants. Instead, those users should authenticate with client credentials. Refer command below:
auth0 login --domain <domain> --client-id <client-id> --client-secret <client-secret>
auth0 login --domain <domain> --client-id <client-id> --client-assertion-private-key <path-to-private-key / private-key> --client-assertion-signing-alg <signing-algorithm>
When your access token expires, the CLI will prompt you to confirm whether to continue with your default tenant or select a different one:
Continue login with default tenant 'your-tenant.auth0.com'? [y/N]
Select y to proceed with your default tenant, or N to choose a different tenant.
Note: Using the CLI will consume Management API rate limits according to the subscription plan. Ref Rate limit Policy
The default text editor is vim on Linux/macOS and notepad on Windows. To change that for editing templates, rules, and actions, set the environment variable EDITOR to your
preferred editor. If choosing a non-terminal editor, ensure that the command starts the editor and waits for the files to be closed before returning.
# Uses vscode with the --wait flag.
export EDITOR="code --wait"
# Uses sublime text with the --wait flag.
export EDITOR="subl --wait"
# Uses nano, a terminal based editor.
export EDITOR="nano"
# Uses vim, a terminal based editor.
export EDITOR="vim"
# PowerShell (current session):
$env:EDITOR = "code --wait"
$env:EDITOR = 'subl --wait'
$env:EDITOR = 'notepad'
$env:EDITOR = '"C:\Path To\executable++.exe" --wait'
# PowerShell (persistent, across sessions):
[System.Environment]::SetEnvironmentVariable("EDITOR", "code --wait", "User")
REM Command Prompt (current session):
set EDITOR=code --wait
set EDITOR=subl --wait
set EDITOR=notepad
set EDITOR="C:\Path To\executable++.exe" --wait
REM Command Prompt (persistent, across sessions):
setx EDITOR "code --wait"
The CLI has an AgentSkills-compatible skill for AI agents (Claude Code, OpenClaw, etc.), available from the Auth0 Agent Skills repository.
The auth0-cli skill is part of the auth0/agent-skills collection. Install the full Auth0 skills suite to get it along with other Auth0 skills:
Claude Code plugin marketplace:
/plugin marketplace add auth0/agent-skills
/plugin install auth0@auth0-agent-skills
Skills CLI:
npx skills add auth0/agent-skills
Manual installation (Claude Code, OpenClaw):
git clone https://github.com/auth0/agent-skills.git
# Claude Code
cp -r agent-skills/plugins/auth0/skills/auth0-cli ~/.claude/skills/
# OpenClaw
cp -r agent-skills/plugins/auth0/skills/auth0-cli ~/.openclaw/skills/
Note: The
auth0binary must be installed and available on your$PATHfor agents to use this skill.
Anonymized data points are collected during the use of this CLI. This data includes the CLI version, operating system, timestamp, and other technical details that do not personally identify you.
Auth0 uses this data to better understand the usage of this tool to prioritize the features, enhancements and fixes that matter most to our users.
To opt-out of this collection, set the AUTH0_CLI_ANALYTICS environment variable to false.
We appreciate feedback and contribution to this repo! Before you get started, please see the following:
To provide feedback or report a bug, please raise an issue on our issue tracker.
Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
<source media="(prefers-color-scheme: dark)" srcset="https://cdn.a
$ claude mcp add auth0-cli \
-- python -m otcore.mcp_server <graph>