Usage percentage displayed in agent window is incorrect

[rsb]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the agent window, the percentage meter showing total usage is inconsistent with the details shown in the Plan & Usage window.

This seems to be a new issue, since the agent percentage was displayed accurately until recently.

Steps to Reproduce

1. Open an agent session in the Editor window after having some plan usage.
2. Compare the percentage value shown with the two component percentage values (Auto + Composer and API)

Expected Behavior

The overall percentage value (“Included in ” in the Plan & Usage window, and the overall percentage value in the agent window (“You’ve used x% of your included total usage”) should be a meaningful combination of the two component percentage values.

They’re not.

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 3.11.19
VS Code Extension API: 1.125.0
Commit: bf249e6efb5b097f23d7e21d7283429f0760b740
Date: 2026-07-12T21:39:24.175Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Linux x64 6.8.0-134-generic

For AI issues: which model did you use?

Likely N/A, but Opus 4.5 with a bit of Composer 2.5 and some GPT5.6 Sol / Terra during this billing period.

Additional Information

There’s a chance that I might have a Cursor credit (@Colin would know) – but I’m not sure where to see if this is the case, and whether it might affect percentage calculations?

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Colin]

Hey @rsb!

I think this is actually expected behavior, not a bug. Your included usage is made up of two separate usage buckets, and those buckets are different sizes.

The first-party bucket is much larger than the API bucket — and it just doubled the other day, so the gap is bigger than ever.

The overall percentage isn’t the average of the two bars, it’s total spend across both buckets divided by the combined budget, so it gets weighted toward whichever bucket is larger. That’s why you can have 1% of the (large) first-party bucket used and 64% of the (smaller) API bucket used, and still land at ~13% overall.

[rsb]

Thanks, Colin. I notice that there’s been a subtle change in the wording of the % meter in the agent window (from ‘included total usage’ to ‘included API usage’) since I wrote this up, but your explanation makes sense:

I like the latter (API usage) displayed in the agent window better, since it lets me know how close I am to falling into the more expensive on-demand usage bracket.

(this is still on Cursor 3.11.19 BTW)