alis accounts¶

Choose your active account: the one account the console, the CLI and the TUI all work in, that your usage in Ideate and Build is measured against, and that is invoiced at the end of the month. For anyone who belongs to more than one account, and for agents that hit ACTIVE_BUILD_ACCOUNT_REQUIRED.

Synopsis¶

Shell

alis accounts list [flags]
alis accounts select accounts/ACCOUNT [flags]

Aliases: accounts, account.

Description¶

An authenticated session must carry an active account before platform commands run. list shows the accounts available for selection; select sets the active account and refreshes your sign-in. Usage you generate in Ideate and Build is measured against the active account, and that account receives the invoice for its users' spend. alis ideate lists, finds and creates projects in it. Switching here switches the console too, and switching in the console switches the CLI. See Accounts and billing.

Subcommands¶

alis accounts list¶

List accounts available for account selection.

❯ alis accounts list [flags]

No flags beyond the global flags.

alis accounts select¶

Set the active account and refresh your sign-in.

❯ alis accounts select accounts/ACCOUNT [flags]

No flags beyond the global flags.

Examples¶

Shell

alis accounts list --json
alis accounts select accounts/<id> --json

JSON output¶

list returns accounts[], each with name (accounts/<id>), display_name and active.

JSON

{
  "accounts": [
    {"name": "accounts/<id>", "display_name": "Acme", "active": true},
    {"name": "accounts/<other-id>", "display_name": "Acme Labs", "active": false}
  ]
}

Notes¶

A command that returns ACTIVE_BUILD_ACCOUNT_REQUIRED (exit 1) needs select first. An agent must ask the user which account should own the usage; it must never choose a billing account on the user's behalf.
Account membership is managed separately from product and build environment access: being active in an account doesn't by itself give you Ideate or Build there.