Installation or launch failure
Use the official download center and match the operating system and architecture. Note the error message before retrying. On Linux, select the package format appropriate to your distribution. On macOS, do not assume an old Intel installer is still the supported build.
Login or network errors
Check whether the account can sign in on the official website. Record the time and error code, and check whether a proxy, VPN or organization policy affects the client. Avoid repeated reinstalls until you have separated an account problem from a local client problem.
Model unavailable or token limit reached
Check the current plan, remaining usage and model picker. Test a small new conversation. If the account has exhausted its allowance, reinstalling the editor will not restore it. Review the price and usage controls before enabling additional spending.
MCP server will not start
Validate JSON, confirm the executable is available to the IDE, and inspect the server log. A shell with a working npx command may have a different PATH from a desktop application. Use the MCP guide for a step-by-step checklist.
Extensions or indexing problems
Try a small project and temporarily disable a suspected extension to isolate the cause. Check workspace size and exclude generated output where the client supports it. Back up settings before resetting anything; keep a short reproduction for official support.
What to include in a support report
Include client version, operating system, architecture, region, plan, the smallest reproduction and a redacted error log. Never attach access tokens, environment files or private source code unless you have reviewed what is being shared.