Documentation
Client and account
The public client authenticates using a browser-approved device code. It stores a short-lived account credential locally. Model routing and provider credentials remain server-side.
Task budgets
Every turn creates a separate task, with a requested ceiling of $1 and a server-authorized maximum. Available credit and the daily ceiling can reduce or refuse the grant. Spending and outstanding holds are reported separately. Unknown charges remain held; no paid retry is automatic.
Scope
Editor and terminal history also stays locally. Submitted task messages and answers are retained in your private service task history. Explicitly uploaded KB documents are stored privately under your account. Other account scopes cannot retrieve them. External Codex and Claude terminal sessions retain their own accounts and quotas.