#Cursor should warn about unpaid invoices before blocking requests

8 messages · Page 1 of 1 (latest)

runic hatch
#

When a payment fails, Cursor currently kills active sessions immediately with no prior warnings, just an abrupt "You have an unpaid invoice" message. This caused me to lose an entire debugging session mid-refactor.

I was deep into diagnosing a crash in a TUI application, progressively removing code with Cursor keeping the reasoning context across iterations. We were making real progress, then the session was terminated instantly. All context gone. The bug still exists, and I now have to redo the entire debugging process from scratch.

The issue isn't that Cursor suspends service for missed payments, That's fair! The issue is that there's zero grace period or warning. A simple heads-up (e.g., "Your invoice is overdue and the service will be suspended in X hours/requests") would have let me wrap up or at least save my progress.

Suggested improvements:
• Show a warning banner when an invoice is overdue, before cutting service
• Allow the current session to finish (or give a short grace window) before suspending
• At minimum, don't destroy active context mid-conversation and let the user see and copy what's already there

simple vine
#

Hey @runic hatch 👋
I got your feedback forward since yesterday

#

When you say that it "kills active sessions", are you able to resume the conversation after the payment, I know that's not really the point but its good to know 🙂

runic hatch
#

my team sorted it quickly, but it's a tricky situation. I can't move on with the project because I can't commit what was broken

#

then I'd lose the context if I change the scope or manually work

runic hatch
#

thank you for the feedback

simple vine
# runic hatch thank you for the feedback

Hey man, really sorry about that 😔
I got a response but their concern is more about the context lost you mentioned:

Unfortunately, when invoices go unpaid, we do need to pause service at some point, and there is never really a great moment to do so.

Once the invoice is paid, the conversation history and any partial output from the session should remain [...] All the agent output should have stayed visible and copyable (even before the invoice was paid).

runic hatch
#

so... I was more reactive when I wrote the post and I didn't lose the context because I trusted that Cursor would keep it, I could if I pressed the revert or accept button.