Authentication

Two ways to sign in:

ardent login opens your browser. Use this on your own machine.
ARDENT_TOKEN is an environment variable. Use this in CI and scripts.

ardent login

Your browser opens to authenticate. Back in the terminal, Ardent selects your project and connector for you if you only have one of each — so you can go straight to ardent branch create.

Example output: one project and one connector

✓ Logged in as username@tryardent.com

  Auto-selected project 'my-app'
  Auto-selected connector 'my-app-db'
  Ready to branch:
  ardent branch create <name>

Example output: multiple projects

✓ Logged in as username@tryardent.com

3 projects found.
Next step: select a project: ardent project switch <name>
List your projects: ardent project list

Tokens for CI

Set ARDENT_TOKEN and run commands normally — no login step:

export ARDENT_TOKEN="sk-ard_..."
ardent branch create pr-123 --print-url

When ARDENT_TOKEN is set, it always wins — even if the machine has a stored login. There’s nothing to clean up first. In GitHub Actions:

env:
  ARDENT_TOKEN: ${{ secrets.ARDENT_TOKEN }}

steps:
  - run: npm install -g ardent-cli
  - run: ardent project switch my-project
  - run: ardent connector switch prod-db
  - run: echo "DATABASE_URL=$(ardent branch create pr-${{ github.run_id }} --print-url)" >> "$GITHUB_ENV"

Create and revoke tokens in the dashboard under Settings > API keys. Keep them in your secret manager, and rotate any token that leaks.

For a one-off login with a token instead of the browser, ardent login --token <your-token> stores it like a normal login.

ardent status

Shows whether you’re signed in, and as whom:

ardent status

Example output

✓ Authenticated
  Account: Username
  Email:   username@tryardent.com
  Org:     Ardent

If you’re authenticated only through ARDENT_TOKEN, status shows a masked token instead of profile details. That’s normal in CI.

ardent logout

ardent logout

Deletes the CLI’s local state file — stored login, API URL, selections, and cache. It does not revoke API tokens; do that in the dashboard.

​ardent login

​Tokens for CI

​ardent status

​ardent logout

ardent login

Tokens for CI

ardent status

ardent logout