Your own vendor subscription

Sign a CLI in with your own account and it runs on your subscription instead of your credit here.

The sign-in

Settings, then AI accounts, then start the sign-in.

  1. The CLI prints its URL
  2. you open it
  3. you paste the code back
Nothing is intercepted or replayed. The path leaves the CLI and comes back to it, because sign-in mirrors each CLI's own flow: it is that CLI doing the signing in.

Once signed in

The credential
Kept in a per-account configuration directory that all your containers share, so one sign-in reaches every node. This service never reads, copies, or backs it up — only the vendor’s own tool does — and it is deliberately left out of snapshots and exports.
The bill
That vendor bills you on your subscription. Nothing reaches your credit ledger.
The limits
Your subscription's own limits apply unchanged. This service does not raise them, extend them, or reroute a request that has hit one.

What does not reach here

Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Legal & privacy · Home