Cursor team is censoring stuff now woah, make the tool bad and not allow saying so
1 Like
Dude, it’s not a bug. The Cursor team has mentioned this on the message boards already. You just don’t know how to use agent mode, which is 99.9% fully automatic.
1 Like
Can you share the post they explain why it takes this much token to make tiny edit, and is their how-to-use-agents guide published?
Yes you must consult with the magic orb 
before every prompt. Takes years of practice to do so effectively.
recent update from the cursor team on the token consumption:
There were 3 tool calls and equivalent token usage to 24 reads soooo
As Enterprise-tier user, I have not this unfortunate problem. Potential hints :
- Are background agents running ? It will skyrocket your agent usage
- Auto is designed at best to make you use the model cursor wants you to use. My first idea was basically to load-balance models usage and by using auto you’d end up using bad models by design.
I admit I never envisioned they could actually do the opposite and make people models’ usage skyrocket by making them use likely max models that burn up 200 seat per request on my enterprise tier…
Cursor must address this quickly by giving clear answers, at this point to apologize without addressing the issue is pointless and hurting cursors’ brand.
Dude, it’s literally a bug: Unofficial Community Discussion to Give Fedback on Plan Rates - #7 by mokhir
92% of total usage is Cache Read. I start a new chat for everything, i only have 1 MCP server which is rarely used, this ain’t normal.
I have the same bug but according to Cursor staff it’s not a bug, it’s a skill issue on our end.
how even this happened?