Troubleshooting

Chat and catalog#

When Chat does not open, users go to Sign in and authenticate again. A signed-out browser can show public pages, but Chat, Files, projects, memory, connectors, and Billing require an active account session. When the model catalog is unavailable, a refresh after checking the network connection can restore the picker. The picker only lists models returned by the current catalog and can show no selectable rows while that request is failing.

Model locks#

When a model is visible but locked, its details identify the reason. Common causes include the Zero Data Retention or no-training filter in Settings → Advanced, a plan gate, or a provider route that is temporarily unavailable. Published capabilities and price are read from the catalog row; a missing value is not a zero value. When the reasoning control offers only None, the selected model does not advertise a reasoning ladder.

Skills and billing#

For Skills & Plugins, users open Skills & Plugins and select Installed. The connector should be installed, enabled for the intended surface, authenticated when required, and supplied with a key when the card asks for one. A desktop loopback requirement means that web and iPhone cannot complete that callback; the first sign-in belongs in desktop Chat or Code. If Billing shows no customer or stale usage, a plan or extra-usage pack selection followed by a return to Settings → Billing refreshes the account state. Manage billing opens the payment provider portal.

Mobile Gateway and Code#

For a paired phone, desktop Settings → Mobile Gateway should show an enabled gateway, an available private route, a QR created after enabling, and a confirmed device. Stale grants can be resolved by checking scopes, revoking the device, and pairing again. The desktop must be signed in to grant a phone. Local Code work remains on the desktop when the phone is offline; the phone cannot invent a completed run. See Remote access, Usage, Skills, and PC.