Profiles

A profile is your login: an access token tied to the Botpress account you authenticated with. Profiles are per-person and never shared or committed.

A profile decides who the CLI acts as. It doesn’t decide which bot a command touches: that comes from how the project is linked to its bots, covered in Project setup. Your login only supplies the credentials.

Signing in

adk login opens a browser to authenticate and saves the result as a profile:

adk login                       # interactive sign-in
adk login --profile work        # save under a named profile
adk login --token <token>       # non-interactive (also reads $BOTPRESS_TOKEN)

You can also sign in from the Dev Console. Choose Sign in with browser to authenticate, or Use a token instead to paste a token:

Switching and removing profiles

If you work across more than one Botpress account, keep a profile for each and switch between them:

adk profiles list           # list profiles and show the current one
adk profiles set <name>     # change your default profile
adk logout --profile <name> # remove a profile
adk logout                  # remove the current profile

To use a different profile for a single command without changing your default, pass --profile:

adk deploy --profile work

For the mental model behind profiles, targets, and project links, see ADK concepts. For every command and flag, see the CLI reference.