Hey, thanks for the detailed report. The screenshots and the Request ID really help.
This is a known cluster of bugs, confirmed:
-
The continuation injector triggers falsely. The client appends “Your previous response was interrupted. Continue from where you left off.” even after a completed reply, and the model then continues. That’s what you’re seeing in the
[8:14:30 AM] User ...blocks. -
The model echoes prompt structure tags like
Human:,<user_query>,</user_query>in the assistant output. These tags shouldn’t be visible as “user messages”, but because the tags in the prompt wrapper aren’t escaped, they sometimes leak out and look like a real user message like[Stop].
The combo of these two bugs creates the token-spending loop you’re seeing. We’re tracking it, but I can’t share an exact ETA for a fix yet. When there’s an update, I’ll post it in the thread.
Similar report and discussion: Cursor automatically injects "Your previous response was interrupted" after every response
About quota usage from this incident: email [email protected] with the Request ID, and the billing team can review your usage and help.
Temporary workaround for now: if you see the loop starting, hit Stop and start a new chat to break the injection. Let me know if you hit it again.