up_ and carry your access across every studio you belong to. Create one under Account > Developer, in the Access keys section.
Log in
login opens that page for you, prompts for the key (input is hidden), verifies it, then saves it as an account in a private file on your machine. If you want to skip the prompt:
Switch between accounts
Log in more than once to keep several accounts side by side. A work login, a personal one, a key pointed at a different API: each stays put until you switch to it.1
Add another account
Accounts are named after your email. You can give one a friendlier label with
--as:2
List your accounts
3
Switch the active account
userplay logout (drops the active one) or userplay logout --as work for a specific one. If you remove the active account and others remain, the next saved account takes over.
Using a key in CI
SetUSERPLAY_API_KEY and skip login entirely. The environment variable beats the active account’s saved key, and it never touches the disk.
--yes on any write that runs unattended.
Where state lives
Credentials and config sit in your OS config directory:
Set
USERPLAY_CONFIG_DIR to move it somewhere else. This keeps a CI job or scratch script from overwriting the credentials you use day to day.
To see everything resolved at once (active account, API URL, whether a key was found and where it came from, config paths):
https://api.userplay.io/public/v1 unless something says otherwise. To point them at a different URL, log in against it with userplay login --api-url <url> --as staging, re-point the active account with userplay config set --api-url <url>, or override a single command with --api-url.
Related articles
Global options
Agent mode, dry runs, and the guards in front of every write.
API keys
Rotate the key this login is holding, or retire it.
Troubleshooting
Still
unauthorized, right after logging in.CLI overview
Install it, and see what the tool covers.