Composer 2 token consumption today feels extremely high (10x normal)

Ideas Feedback
1

Hey all I experience some excessive Composer 2 token consumption today - wanted to know if anyone had similar experience.

I have been working in my codebase for about 6 months now and have a good handle on what types of tasks or builds consume what amount of tokens and what it costs me.

I wouldn’t be writing this unless it was shocking - I performed a build today

  • 1 rule applied
  • ~30 document reads
  • ~15 document edits

Token consumption was 4.5M at a cost of $5.50!

Similar tasks in the past have been easily 1/10th consumption and I would expect it to take. Similar tasks in the past on both Composer 1.5 and Composer 2 have been more akin to $0.5 to accomplish. Is anyone experiencing the same today?

6

Hi Zach,

Thank you for reporting this. Do you feel comfortable sharing the request ID with me? If you have privacy mode enabled, do you mind switching it to Share Data in Cursor Settings, re-creating the issue, and then sharing the request ID with me? This will help me take a closer look at the request and see if something is going wrong. Cheers!

7

Hey Kevin so sorry asked my security team and got a no-go on the privacy mode switch .

1 Like
8

Hey,
I just found this thread when searching for exactly this issue. My token usage exploded massively too. Super simple requests in a new project. Last 3 request with 400k - 3,7m tokens - never above 100k before.
I’ve enabled data sharing - here is my request_id: 93d5043f-4763-49ed-bd02-cb51d5250211
Something seems off

image
image2056×1080 164 KB

9

He @Nicolas_Heiligenthal really appreciate you hopping in here and sharing your session - wish I could as well but my hands are tied there.

Want to communicate I switched to Sonnet 4.6 with more consistent results to my previous experience with Composer. Will revisit Composer 2 in several weeks to see if it’s improved.

10

Hi @Nicolas_Heiligenthal Thanks for sharing the screenshot and the request ID. I can’t see information about your requests because of your current privacy mode settings. If you feel comfortable, do you want to disable privacy mode temporarily and see if you can re-create a similar request that generates this potential issue? You can re-enable privacy mode immediately after.