blossom login
Login with Blossom
Usage
blossom login [--new-profile NEW_PROFILE] [--token TOKEN] [--no-browser]
Flags
| Flag | Description |
|---|---|
--new-profile |
Create a new named profile without switching the current selection |
--token |
Use an API token instead of browser login |
--no-browser |
Print the login URL instead of opening a browser |
Examples:
blossom login
blossom login --new-profile prod-tung
blossom login --new-profile prod-tung --no-browser
BLOSSOM_API_URL=https://app.blossom88.dev blossom login --new-profile dev-tung
blossom login --token blossom_access_...
With a selected profile, login renews its credentials. Approval must match its
saved Account and API endpoint; login cannot move it to another Account.
With no profile selected, login creates and selects one using your username
(email prefix or display name as fallback). Taken names get -2, -3, and so on.
Use --new-profile NAME to create another profile through the same flow as
profile:create --name NAME --login. The name must be unused. This explicit
creation leaves the current selection unchanged and prints the next command:
blossom profile:use --name prod-tung
New profiles default to https://app.blossom88.com, independently of the selected
profile. Set BLOSSOM_API_URL to choose another deployment. Existing profiles
keep their saved endpoints.
Browser approval creates and saves the login credentials automatically. The URL
and code are always printed; SSH and headless sessions skip opening a browser.
--no-browser forces the printed-URL flow. Check the Account and code before
approving. Denial saves no profile or credentials.
Use --token for an existing API token, including with --new-profile.
CI requires a token; plain browser login needs an interactive terminal or
--no-browser. Settings and credentials are stored separately under
~/.config/blossom/profiles/ and ~/.config/blossom/credentials/.