Composer Stuck at "Generating" - Specific Composer Instance, Not Global Issue

Hey, I can’t see this request ID internally, which suggests their is some networking issues stopping Cursor from connecting to our servers.

Can you run the Developer: Toggle Developer Tools command to show the console, and look for any errors there related to your connection issues?

@danperks This is the error that occurs when I run a command
Thank you for your feedback

What’s surprising is that when I click “Send”, I don’t see any network calls or logs. It’s like no requests are being sent.
I only get errors when I timeout or click stop.

Update : When I click “Attempt Update”. :down_arrow:

image

Update 2 : Only chat mode works, Edit & Agent stuck at “generating” no messages on chromium console.

If I use “Fix in chat” :down_arrow:

Update 3 Final : I think I’ve found the culprit.
It’s a file generated by Composer that has problems opening and closing ", ], }, which causes Cursor to malfunction.
In other words, the code in the file was directly affecting cursor.

If you need the file to prevent this from happening again, I can send it to you.

About my config :

Version: 0.46.8
VSCode Version: 1.96.2
Commit: be4f0962469499f009005e66867c8402202ff0b0
Date: 2025-02-28T19:31:35.681Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

Sorry for the delay!

I’m glad you have figured out the culprit, although the code contents shouldn’t affect whether the Cursor works correctly or not - I’ll flag this to the team to take a look into.

This still appears to be an issue, and for me seems to have gotten much worse over the last day or two. At this point, I can’t get much done because Cursor continues to get stuck “Generating…”. I can stop, and ask it to try again, and it will, and then again it will get stuck.

Edit: After further testing, I think this might be caused by our use of an AWS VPN.

Is there a way to get a list of all of the domains that should be white-listed so we can be sure the VPN is allowing all necessary traffic?

It’s still not resolved! :frowning: