So I can match this to the right bug report on our side (over the last few weeks, this thread has collected a few different issues with similar symptoms), can you confirm:
Your current Cursor version and OS from Help > About
Your layout, editor or glass, also in the About section
Are you running in worktree mode or normal mode?
When you say it got worse after the last update, what version were you on before, and what version are you on now?
Also, this thread has grown and now has multiple different bugs under one title (HTTP/2 proxy, worktree timeout, Opus 4.7 hang, Provider Error, Network disconnected). If what you have now is just a hang in a new chat without worktree, please open a separate topic with the info above and the Request IDs. That’ll help us move faster without mixing symptoms from other reports in this thread.
Basically, almost every conversation now runs into “taking longer than expected…”. When I send “continue” and wait for a while, the exact same issue happens again, making it impossible to make any progress. Meanwhile, the API usage keeps going up the whole time, which is extremely frustrating. I tried both Codex and Claude Code, and neither of them has this problem.
This issue existed before, but recently it has become extremely frequent, to the point where Cursor is basically unusable. I upgraded to the latest version and also tried older versions, but the same problem persists. It occurs on both my work and home computers, and one of my coworkers also reported encountering the same issue.
Hey, thanks for the diagnostics. They all show Success, so it’s not a network issue. Let’s keep digging.
First thing I notice: you’re on 3.0.16 from April 9, which is pretty old. The current stable is 3.2.21+. There have been a few fixes in this area over the last month. Please update first via Help > Check for Updates or download from Cursor · Download, then check if it still reproduces after the update.
If the hangs keep happening on the latest version, the symptom hang after a long chat, mostly on Opus is a known issue we’re tracking. I can’t share an ETA for a fix yet. Workarounds that often help:
Start a new chat with Cmd+N instead of continuing a long thread, especially if it had images and MCP calls
Temporarily switch to Claude 4.6 Sonnet or GPT-5 for long-running tasks
If the bug is still there after updating, please create a separate topic. This thread already mixes a few different bugs under one title and they’re getting in the way. In the new thread, include:
Request ID from the hung chat (top right of the chat menu > Copy Request ID)