Cursor’s Undisclosed Model Upgrade Issue

[iCoder]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

This is a critical service issue. The claude-4.5-opus-high model within Cursor was suddenly switched to MAX mode without any prior notification, no in-product alerts, and no indication during model selection. This unexpected change caused my usage quota to be consumed almost instantly.

A platform handling metered, high-cost models must not modify model behavior or pricing tiers silently. Any elevation to MAX mode requires explicit user consent and clear UI messaging. The absence of disclosure directly impacts cost control, capacity planning, and trust in the service.

I request a formal explanation of why this change occurred without notification, how such risks will be mitigated going forward, and an adjustment for the unintended consumption caused by this undocumented model switch.

Steps to Reproduce

Cursor silently switched claude-4.5-opus-high to MAX mode with no warning, instantly draining my usage.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.14
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Colin]

Hey there @iCoder

I saw you were switching between Opus 4.5 and Composer.

These three controls are very close together — the MAX Mode toggle, Composer 1, and Opus 4.5 selection. Is it possible you accidentally clicked the MAX Mode toggle when switching models?

Not saying we can’t do better here. Your idea of requiring explicit confirmation is an interesting one!

[iCoder]

Hi Colin

I reported this to Rose via [email protected]