Skip to main content

Troubleshooting

Adding an account shows a warning

Newer builds show connection and usage warnings separately. An orange connection warning means the key or connection could not be verified; check the entered details and provider access. A yellow usage warning means quota or billing information could not be read, which does not block model requests. Save anyway keeps the account; Go back lets you correct its settings. Saving does not bypass an extension's required endpoint approvals.

If Could not check endpoint approval replaces the entire API-key form, update Glixo Code and its connected Service or runtime. Current builds keep ordinary key entry available when that metadata check fails.

No models appear

Open Settings → Providers & models and check that the account is connected. Reopen its details and refresh the model list if that action is available. Confirm the provider account has access to models and that the selected machine is online. If the provider rejected the key or sign-in, reconnect it from the account settings.

Usage is missing

Usage not reported or Balance not reported does not mean zero. Gemini API-key connections and existing CLIProxy connections do not currently supply account quotas or balances. OpenAI API spend needs a separate Admin key; Anthropic organization reporting needs eligible reporting access. See usage support by connection.

Unavailable means Glixo could not retrieve the status; open the account details and select Refresh. Saved or Stale snapshot means the numbers are from an earlier check. If a local Android usage refresh returns 404 Not Found, update the Glixo Service as well as the Code app: an older Service may not implement the usage route. A missing usage route is separate from a provider rejecting your key.

A request says you have no credits or quota

Check which provider account the session used. A subscription quota and API billing are different provider products. Wait for the displayed reset time, choose another account with available access, or resolve billing with the provider. A Glixo sign-in does not add model-provider credits.

OpenAI ChatGPT/Codex plan credits cannot fund ordinary OpenAI API-key requests. Select the ChatGPT/Codex connection to use that plan, or configure API billing for the API-key account. To test the account you intended, turn Provider fallback Off and send a small request.

An existing CLIProxy server is not detected

A green dot indicates a detected local server, not an authenticated provider. If there is no dot, check the server URL and whether CLIProxy is running. For a remote server or a custom port, enter its actual URL and server API key. The session machine must be able to reach it; localhost on Android Run here refers to the phone, not your computer. Missing usage on an otherwise working existing proxy is expected with its inference key alone.

The machine or project is missing

Open the machine list and confirm the machine is online. Refresh it after reconnecting Glixo Code on that computer. Check that the project belongs to the signed-in Glixo account and is present on the selected machine.

A command or file change failed

Read the complete error in the session, open Terminal to inspect command output, and open Diff to see which files changed. Ask Glixo to explain the failure before retrying a command that could overwrite or remove data.

An extension cannot be installed

Check the catalog entry’s app version, platform and installation status. If Glixo marks it unavailable, use another supported extension or ask its publisher for a compatible release. Do not rename an archive to bypass the app’s install checks.