I use Opus 4.6 High and it consumes 2 credits (requests) per request. Maybe the Max version is taking 3 credits usually.
While I got no idea if Cursor documented this or not..
My past usage takes 2 requests for this model. The issue I am trying to convey here is that that despite this single request gets halted it consumed me 3 times the usage it should have taken.
If you meant it used 3 times the usage it should have taken (by terminating the agent run and sending new request) then yeah thats consuming and it should be solved. For me it doesn’t happen a lot so I’m kinda ok with it. Does that happen with you oftenly?
If a single turn of request gets halted in the middle I’m happy with cursor counting that as consumed, what I am a bit concerned about is that one request gets counted multiple times. This could mean other requests might have been miscounted unknowingly.
Thanks for reporting this with the request ID – I was able to trace exactly what happened.
Your request experienced repeated connection drops (HTTP/2 stream disconnects) on the server side. Each time the connection dropped, the client reconnected and the reconnection was billed as a separate request – that’s where the 3 charges came from. This is a known issue our team is actively investigating.
A couple of things that may help reduce the likelihood of this happening:
Update to the latest version of Cursor – you’re on 2.6.19, and newer versions include connection stability improvements
Try HTTP/1.1 mode: Go to Cursor Settings > Network and switch the HTTP Compatibility Mode to HTTP/1.1. This avoids the HTTP/2 stream behavior that caused the disconnects
Start fresh conversations periodically – your session had a very large conversation state, which can contribute to connection instability
If this keeps happening, feel free to share additional request IDs, and we’ll investigate further.
