Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
With a Grok model selected, the usage UI shows the Other models meter. Grok 4.7, Grok 4.6, and Grok 4.5 are Cursor Models and should be shown against the Cursor Models pool.
Steps to Reproduce
- Sign in on a plan that includes both pools (Pro, Pro Plus, or Ultra).
- Open the usage UI (editor settings or the Spending tab).
- Select a Grok model (Grok 4.7, Grok 4.6, or Grok 4.5) and send a request.
- Watch which meter the UI presents for that usage.
Expected Behavior
Selecting Grok shows and updates the Cursor Models meter. The Other models meter stays unchanged for that usage.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
Version: 3.22.12 (system setup)
VS Code Extension API: 1.128.0
Commit: 3a92974361033b2051526321308c2740fe5912c0
Date: 2026-09-26T04:55:12.125Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200
For AI issues: which model did you use?
Grok
Additional Information
Docs list Grok 4.7, Grok 4.6, Grok 4.5, and Composer 2.5 under Cursor Models, and third-party models under Other Models. Spillover onto Other Models is expected only after the Cursor Models allowance is used up. Subagent or helper calls that run a third-party model can also land in Other Models. This report is about the meter shown for the Grok request itself.
Does this stop you from using Cursor
No - Cursor works, but with this issue

