brama subscription handover¶
Sign every account the pool holds and a coding-agent harness on this machine lacks into that harness. An account acquire bought is in Brama’s pool; the agents that spent the old accounts run in a harness with its own credential store, and this is how they get the new one.
No grant crosses machines. For each missing account the command starts the harness’s own login (omp login anthropic), reads the authorize URL it prints, and asks Weles (POST /reauth/authorize, Brama’s admission token) to complete that authorization as the account. Weles drives only the provider’s authorize page redirecting to the harness’s localhost listener, catches the redirect in its browser and answers it; the command hands that redirect to the login on stdin, and the harness mints and refreshes its own grant with the verifier only it holds. Brama’s grant is never shared with it.
Nobody has to run it: installing the Brama CLI through Stado (stado product install brama --surface cli) declares a schedule pinned to that machine that runs brama subscription handover claude-code --harness omp every minute, so an account a maintenance pass bought reaches omp on the operator’s machine without anyone typing a command. On a machine where omp is not installed the command answers omp is not installed on this machine, so no account is signed into it here and succeeds.
Invocation¶
brama subscription handover <PROVIDER> --harness omp [--json]| Input | Required/default | Meaning |
|---|---|---|
<PROVIDER> | required | The pool provider whose accounts are handed over: claude-code (omp calls it anthropic). |
--harness omp | required | The harness on this machine to sign in; its accounts are read from omp usage accounts. |
--json | optional; off | Print {"provider", "harness", "ok", "accounts": [...]} instead of lines. |
Output and state¶
One line per pool account: held (the harness already had it), handed_over (signed in now, and listed by omp usage accounts afterwards), failed with the reason, or unattributed for a member that records no account. Weles’s stages print on stderr. The command exits 0 only when the harness lists every account the pool holds. The new account is in omp’s own store, so omp usage shows it and omp balances sessions onto it.
Refusals¶
A provider the harness has no counterpart for is refused with omp has no account of Brama’s provider `<provider>` to sign in. A login that prints no authorize URL fails that account with everything it printed; a login that exits non-zero after the redirect fails it with its exit status and output; an account the login reports signed in but omp usage accounts does not list fails as the harness login ended successfully but `omp usage accounts` does not list the account. Weles’s refusals (authorize_url_refused, authorization_incomplete, an unresolvable account) are reported in its own words.
See the command group or the CLI tree.