As if launching Cursor for the first time

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Error — “check internet or VPN”; Cursor doesn’t execute commands in chat
I check the connection — everything is “green”; I checked several times
Closed Cursor, opened Cursor — greeted with the first-launch welcome window
This has happened for the 2nd time in the last 7–10 days
What’s this for?

Steps to Reproduce

Start Cursor

Expected Behavior

Executing my vibe-coding-in-chat commands

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69 (user setup)
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. The combination of connection errors and the welcome screen reappearing suggests possible settings corruption. Let’s try these steps:

  1. Disable HTTP/2 (most common fix):

    • Open Cursor Settings Ctrl+,
    • Search for “HTTP/2”
    • Enable “Disable HTTP/2”
    • Restart Cursor
  2. Check Windows Firewall:

    • Windows may need to re‑allow internet access for version 2.0.69
    • Windows Security → Firewall & network protection → Allow an app
  3. If you have MCP servers configured:

    • Disable the ones you’re not using (Cursor has an 80‑tool limit)
  4. Check disk space:

    • Low space during updates can corrupt settings
    • Make sure there’s enough free space on the C: drive

If this doesn’t help, please share:

  • Network diagnostics results (Cursor Settings → Network → Run Diagnostics)
  • Request ID from a failed chat attempt (Chat menu → Copy Request ID)
  • Any console errors (Help → Toggle Developer Tools → Console tab)
  • Cursor logs (if there are errors):
    • Windows: %APPDATA%\Cursor\logs
    • Or via command palette: Ctrl+Shift+P → Developer: Open Logs Folder — share the latest ones

Let me know if disabling HTTP/2 resolves it!