Skip to content

[Bug]: Cursor unified plans still show separate usage meters and two-pool wording #34426

Closed

Description

@CsengerBari

Before submitting

  • I searched existing issues and did not find a duplicate of this unified-plan display issue.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web — Usage → Limits (Cursor)

Steps to reproduce

  1. Connect a Cursor account on a plan with a unified usage allowance.
  2. Open Usage → Limits in T3 Code.
  3. Inspect the Cursor usage meters and their explanatory text.

Expected behavior

For a unified Cursor plan, show one meter for the shared allowance and wording that reflects that plan. Do not present that allowance as separate pools or imply that there is additional independent capacity.

Keep separate pool meters where the account's plan actually has separate allowances.

Actual behavior

Even on a unified plan, T3 shows separate Overall and Cursor Models meters. Both show the same remaining percentage and reset time, while the helper text still describes multiple allowances.

The supplied screenshot shows:

Meter Remaining Reset
Overall 96% left 6d 17h
Cursor Models 96% left 6d 17h

The helper text reads:

  • Overall: “Combined usage across both allowances, not a third quota.”
  • Cursor Models: “Grok and Composer use this first. Auto can use either pool.”

For this unified-plan account, the duplicated meters and two-pool wording make the allowance structure confusing.

Impact

Minor bug: misleading quota presentation. This report concerns the display and plan-specific wording; no incorrect billing or quota arithmetic has been demonstrated.

Version or commit

Installed macOS desktop version at the time of reporting: 0.1.8-nightly.20261109.4399.

Environment

T3 Code desktop on macOS, Cursor provider, unified usage plan. The exact commercial plan name was not supplied.

Screenshots, recordings, or supporting files

The reporter supplied a screenshot; its visible meter values and helper text are transcribed above.

Related issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions