When generating and applying a code change, the UI enters a “Taking longer than expected…” loading state and the cursor/spinner keeps running indefinitely. The operation never completes or returns control, leaving the session stuck.
Steps to Reproduce
Use GPT-5.3-Codex and if it think for more than 3 turns, the bug will appear. The bugs won’t appear in 2.1.50, but you sunset that version, forcing users to upgrade and all the versions after 2.1.50 will have the bugs that agents will get stuck after working for a while.
Hey, thanks for the report. A few things that would help us narrow this down:
Does this happen only with GPT-5.3-Codex, or also with other models (e.g. Claude)? If it’s model-specific, that’s useful to know.
Next time it hangs, could you grab a Request ID? Click the context menu (top-right corner of the chat) and select “Copy Request ID”, then paste it here.
Also - when it gets stuck, does cancelling/stopping the request work, or is the entire UI frozen?
The team is aware of related spinner hang issues. Your report helps with prioritization - the model + multi-turn detail is especially useful. Let me know the above and we’ll go from there.
@deanrie I have the same problem, it started yesterday. Instead of a response, I get an endless message “Taking longer than expected…” Request id - 8e9abc91-c3ad-4314-a815-b59d7c54349d
Hey,
I’ve been experiencing the same issue since yesterday.
Request id: f5f140da-7b73-45f6-bac2-d86d16802d15 .
Is there an ETA for a fix?
Thanks in advance.
@Fernando-Fernandes How do you downgrade? I’m still running into the same issues. It can stay broken for hours, and it’s completely unpredictable. It fixes itself and then breaks again randomly.
The solutions the Linear team suggested didn’t work for me.
I am also facing the same issue. I am on Mac and Currsor version is
“Version: 2.5.25 VSCode Version: 1.105.1”.
Issue can be replicated with both Opus 4.6 & GPT- 5.3 Codex
Download version 2.4 from Cursor · Download and install the package. Then, confirm that you want to rewrite the currently installed version.
Unfortunatelly adding “update.enableWindowsBackgroundUpdates”: false in settings.json, per other user in this forum, did not preclude further automatic updates. Still looking for a solution for this.
Hi Fernando, thanks for your help. I can confirm the problem is solved with the version. I have to reinstall it every now and then because of Cursor’s automatic updates.
