Accounts, models, limits and /status

Read status

Type /status in the composer and select its suggestion. It opens a local read-only account/model/usage panel without sending a message or preparing an engineering candidate. It is intentionally not a command-palette action. If it does not appear, inspect composer/runtime diagnostics rather than sending the string to the AI.

Understand the numbers

Distinguish account plan, provider/model, selected effort, subscription allowance, managed customer API usage, credits and reset periods. An unavailable value is unknown, not unlimited or zero. Time windows and reset dates matter; stale cached values need a refresh. The installed runtime/account catalog determines model availability, defaults and pagination. A model from another account is not proof of availability here.

Customer account

Use the website Account flow only when its availability gate permits signup/login. Complete activation on the intended device and check the displayed binding. Billing and quota information comes from the managed gateway and canonical plan policy; the pricing website is not an independent source of entitlements. A subscription is not authorization for paid customer API calls. Cancellation, export and deletion have separate consequences; see Customer journey.

Updates and troubleshooting

Codex runtime updates and app updates are distinct. Read actual update status; failure/offline status must remain explicit. Refresh account state after switching or reauthentication. Never paste credentials into a prompt, screenshot or support log. Owner-development authentication must not silently fall back to customer mode. See Availability.