ap auth

What ap auth covers

Agenda Panda supports both interactive browser auth and non-interactive API key auth. It also supports multiple saved profiles so you can switch between accounts without re-copying keys.

ap auth login

ap auth login

Use this when you want the CLI to authenticate you directly.

ap auth login
ap auth login --key ap_abc123
ap auth login --manual

• ap auth login starts the device-auth browser flow
• ap auth login --key ... stores a known API key directly
• ap auth login --manual prompts you to paste a key without echoing it

Agenda Panda saves successful logins as reusable profiles keyed by email.

ap auth status and ap whoami

ap auth status
ap whoami
ap auth status --json

These commands show the current user, plan, active project, and saved-account status. ap whoami is a shorter alias for ap auth status.

ap auth switch

ap auth switch --list
ap auth switch --name work@example.com
ap auth switch --add --name staging --key ap_abc123
ap auth switch --delete --name staging

Use profile switching when you work across multiple accounts, workspaces, or environments.

ap auth api-keys

ap auth api-keys list
ap auth api-keys create --name github-actions
ap auth api-keys revoke <id>

Use API keys for CI/CD, local scripts, and agent workflows where browser auth is not practical.

ap auth logout

ap auth logout

This clears the stored login plus the saved active project and connection defaults.

Notes

• AP_API_KEY takes precedence over the saved login for the current shell session.
• Config lives at ~/.config/agendapanda/config.json.
• AP_API_URL must be HTTPS unless you are targeting localhost during development.