Cursor v1.6.x Networking Issue

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After updating to Cursor v1.6.x (released mid-September 2025), AI mode stopped working.

• Cursor repeatedly attempts to connect to api.cursor.sh endpoints that no longer resolve via public DNS.
• Network requests to api.cursor.com succeed, but the client still hard-codes calls to api.cursor.sh or api2.cursor.sh, resulting in errors.
• This prevents AI features from functioning, even though my local Python execution runs fine.

Steps to Reproduce

  1. Install Cursor v1.6.x on macOS (tested on macOS [insert version you use, e.g. Sonoma 14.x]).
  2. Open any Python file and switch to AI mode.
  3. Run a script and wait for AI to respond.
  4. Observe console/network inspector → repeated attempts to api.cursor.sh (DNS fails: NXDOMAIN / No Answer).
  5. AI request hangs or fails; stop button shows errors in dev console.

Expected Behavior

• AI requests should be routed to a valid and resolvable backend (e.g. api.cursor.com), and AI mode should return results.
• DNS resolution for the configured API host should succeed without manual edits to /etc/hosts.

Screenshots / Screen Recordings

Screenshot 2025-09-24 at 14.15.28.png
Screenshot 2025-09-24 at 14.15.28.png3048×2060 1.74 MB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z (1 day ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Default provider: Cursor (cloud)

For AI issues: add Request ID with privacy disabled

• Could not retrieve a valid Request ID, since requests to api.cursor.sh never completed.
• See attached console/network screenshots for failed requests.

Additional Information

• Verified connectivity:

  • curl https:// api.cursor. com returns 200 OK.
  • curl https:// api.cursor.sh fails with “Could not resolve host”.
  • curl https:// repo42.cursor.sh connects but returns 404.

• Tried multiple DNS resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, OpenDNS 208.67.222.222, Google 8.8.8.8) → all fail to resolve api.cursor.sh.
• Reinstalling and clearing /etc/hosts entries did not resolve issue.
• Downgrading to Cursor v1.55 works — AI mode executes local scripts and responds, but doesn’t attempt calls to api.cursor.sh.
• Logs: see attached screenshots and cursor-netlog.json.

2

hi @renochoi and thank you for the detailed bug report.

For most such issues the cause is DNS or network providers filtering. Note that this issue may affect only very few users, as we do not have server outages at this time.

Since curl requests succeed I would suggest trying HTTP1.1 mode in Cursor Settings > Network and perhaps trying HTTP2 with curl as well.

3

Thanks for the follow-up, @condor.

I tested your suggestions (HTTP/1.1 mode in settings and running curl with HTTP/2) across multiple networks—including tethering from three different phones in addition to my home WiFi—but the issue remained consistent.

The good news is that after updating to the following latest version today, everything is working smoothly again.

Version: 1.7.28
VSCode Version: 1.99.3
Commit: adb0f9e3e4f184bba7f3fa6dbfd72ad0ebb8cfd0
Date: 2025-10-01T02:45:21.769Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0