What is happening with Cursor at the moment?

Support Bug Reports
1

Describe the Bug

For some reason I could not auto update the software, I just installed it again from the website download and now I can’t actually get cursor chats to do anything at all. I am an Ultra user and I am getting these issues all of a sudden, come on Cursor what’s happening to your updates?

Steps to Reproduce

Just try and chat, it fails constantly and does not send anything to the LLM and therefore sends nothing back!

Expected Behavior

To work!

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.3 (Universal)
VSCode Version: 1.99.3
Commit: e50823e9ded15fddfd743c7122b4724130c25df0
Date: 2025-08-08T17:34:53.060Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Try Cursor Settings > Network > Run Diagnostic

3

Hey, does this happen in all your projects? Could you create a new one and work in it for a while to make sure the issue still persists?

4

that’s not the solution, thanks

5

I agree. I updated to 1.4.3 and now I spend more time telling it what its doing wrong and trying to fix the damage it causes to my code, than actuall deveopment anymore.

6

yeah its becoming somewhat unreliable at the moment, lets hope for a quick fix.

7

Hey, are you still having issues?

If so, can you run the Developer: Toggle Developer Tools command, and check for any errors?
Also, can you confirm that the Diagnostic test showed a good connection?

8

hey yes my connection is 100% fine.

At the moment I am working OK but using GPT-5 for testing that Model, i think some issues were being made when in “auto” model mode.

I think that the main problem is the Specstory extension that was enabled, I have removed this one and now I think we are all OK.

Rob

9

Good to hear! We unfortunately can’t guarentee the stability of 3rd party extensions, or their effects on the performance of Cursor, but it’s good to hear you have it resolved for now!