I ran out of credits, then immediately upgraded my subscription.
Two issues happened:
Cursor puts the original first prompt in the chat, which is clearly a bug when there were multiple turns since (why would even put anything in the chat prompt?)
Cursor rolls back the conversation a couple of steps, so I lost substantial progress
I asked the agent what was the last message it received and it was repeating a message from several turns back.
I asked the agent whether it can find the missing messages, it found them in the local transcript and was able to pick up from there.
Steps to Reproduce
run out of credits with your current subscription
upgrade to a higher package and try to resume the conversations that stopped
Expected Behavior
Cursor doesn’t lose progress/data when runs out of credits.
Hey, @afsuk, thanks for the detailed report. Losing progress in the middle of a chat really sucks, I get it.
What you’re describing, the chat jumping a couple steps back and the input box restoring an older prompt, sounds like how the app currently tries to recover when sending a message gets cut off because usage ran out. That shouldn’t happen, and it’s not something in your setup, I’ve passed it to the team.
To help narrow down the trigger, can you share a couple details?
After upgrading, did the Cursor window reload or restart before you noticed the rollback?
Did you click Resume or Try again on the error card, or did you just send a new message?
If the chat is still open, the Request ID of the last response: chat menu in the top right > Copy Request ID. If you have Privacy Mode on, the ID might be unavailable, that’s totally fine, just skip it.
The window didn’t reload. I tried restarting later, so it might bring back the full conversation, but it didn’t. (I restarted after asking the agent what was the last message it saw and confirming that multiple turns were lost)
I clicked Resume
Current last request id: 13c58c9e-08d2-4924-8f80-6f87a56db6ae (for previous ones cursor says “request ID not found”).
Thanks, these details are exactly what we needed. The fact that you clicked Resume and the window didn’t reload really helps narrow this down. It looks like the rollback happens specifically in the recovery path after a send fails due to hitting the usage limit, and Resume then attaches to the wrong message. That would explain why it jumps back to the first prompt and why you lose a few steps.
I shared this with the team along with the Request ID. This is an issue we’re tracking. I can’t share a timeline yet, but I’ll post here if there’s an update.
A couple practical notes for now:
You already found the best recovery method. Ask the agent to pull the missing messages from the local transcript and continue from there. That’s a solid workaround if it happens again.
If you hit the limit again mid-chat, after upgrading try not to press Resume. Instead, just send a new message in the same chat. Based on how this works, that seems less likely to mess with the history. No promises, but as a temporary workaround it should help avoid the rollback.
Let me know if anything changes after the upgrade or if anything else comes up.
Got it, thanks for the clarification, that’s an important detail. So Resume didn’t roll back to the very first prompt, it rolled back 3 to 4 turns. I’ll pass this to the team so we have the right picture.
Everything else stays as agreed. If you hit the limit again mid-chat, after upgrading it’s better not to press Resume. Just send a new message in the same chat, there’s less chance it’ll affect the history. And if anything gets messed up, ask the agent to pull the missing messages from the local transcript, like you did before.
I’ll reply here if there’s an update. Let me know if you run into it again.