Account / agent defaults keep reverting to 500K context + High/Fast every other week

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

My preferred defaults are 256K context, High effort, Fast off. Roughly every other week they silently flip back to 500K + High/Fast. I catch it after usage spikes (once ~20% of my pool in about an hour). I’ve had to reset this at least twice already, including again today.

This is not me changing models mid-chat. It’s the saved default coming back as the expensive variant.

Steps to Reproduce

  • Set preferred defaults to 256K, High, Fast off here: https://grok.com/dashboard/cloud-agents

  • Use Cursor / agents normally for days or weeks. (it’s pretty random that it swaps back but likely lines up with some release cadence you guys have)

  • Without changing those settings, notice defaults are again 500K + High/Fast.

  • Reset; later it happens again.

Expected Behavior

Explicit defaults stay put across updates and sessions until I change them. 500K / Fast should never become the silent default after I opted out.

Operating System

Other

Version Information

Cursor Cloud Agent Settings found here: https://grok.com/dashboard/cloud-agents

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @devyMcDevFace, I found what’s flipping it. Your dashboard setting isn’t being reset by an update. If you use the Cursor app on iPhone, the app rewrites your saved Cloud Agent default to Grok 4.7 High with Fast on when it loads its model list, and that replaces the 256K / High / Fast off choice you saved on the dashboard. Cloud agents started after that (including ones Grok Bot launches) then run on the Fast variant, which fits the usage jumps you saw. I’ve passed this to the team.

In the meantime, after you re-save the default on the dashboard, check it again after you next open the iPhone app. You can also tell Grok Bot which model to use when it launches an agent, so it doesn’t fall back to the saved default.

Yep that’s it. I was able to verify it just now. So I’ll just not use the app for a bit I guess haha.

Thank you @Colin for the quick diagnosis looking forward to when that gets fixed!