The app won’t open
Preview builds are unsigned, so the first launch shows a warning. On Windows choose More info → Run anyway. On macOS use System Settings → Privacy & Security → Open Anyway. If an AppImage says “Permission denied”, run chmod +x on it first. Getting started has the details.
The model doesn’t respond
Check which provider and model the chat is using. A missing key, an expired sign-in, a local model that hasn’t loaded, a network problem, and a rejected request each look a little different, and the error message usually says which. Settings → Providers shows which connections are working.
A model appearing in the list doesn’t guarantee it supports every feature. If a model struggles with tools or images, try another.
You hit a provider limit
Your provider controls balances, plans, and rate limits, so check your account there before retrying again and again. Free models can run out of capacity. If you switch providers, check what the new one can do and what it costs.
Earlier data is missing
The chat’s Python session may have restarted. Ask the model to check what is there now, then look for saved files or checkpoint values. Overview → Python shows which sessions are live. Checkpoints are off by default; see State & continuity.
A browser or app task is stuck
Look for a first-time setup step, a browser or profile choice, or a prompt in the other app. If you use a copy of your personal browser profile, close that browser and try again; VARIANT-1 won’t close it for you.
Before repeating a click, a save, or a send, find out whether it already happened. A missing confirmation doesn’t always mean the action failed.
A task was interrupted
Check what finished, what stopped, and what might still be running. Stopping doesn’t undo changes, so if the result of an action is unclear, look at its destination before trying again. Then tell the model exactly what is missing; a full restart is rarely needed.
Report an issue
- The app version, your operating system, and your processor type.
- The provider and model you used, never your keys.
- What you expected, and what happened instead.
- Steps that reproduce it, using sample files.
- The error you saw, after checking it for anything private.
Open an issue on GitHub. For security problems, follow the security policy instead.