Hey, thanks for the report with the screenshot and Request ID, I’ve got everything.
This is a known bug with the continuation injector. In some cases it falsely triggers on an already finished response and adds a hidden “previous response was interrupted”, which makes the model generate a new turn on its own. We’re tracking it, but I can’t share an ETA for a fix yet. I linked your case (Windows + Opus 4.7 Extra High + long context 74 to 75 percent) to the ticket, it’s a useful signal since most earlier reports were macOS or Sonnet.
Related thread with more details: Cursor automatically injects "Your previous response was interrupted" after every response
For now, workarounds:
- If it starts looping, start a new chat. The bug is tied to the state of a specific conversation.
- Try not to let the context grow too much. It triggers more often in long sessions.
- If it reproduces reliably on one model, try switching to another one like Sonnet and see if it happens there too.
About usage, yes, each of these “continued” turns is a real request and counts toward your limit. If you hit your limit because of this bug, email [email protected] and we’ll see what we can do.
We’ll post here once we have an update on the fix.