Bug: composer 1's input tokens are not charged i.e free

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

hey @cursor team, there is bug that i just came across

in agent mode when using Composer model, input tokens of my session is not getting counted correctly
there are 2 scenarios

  • input tokens are counted as output tokens
  • or input tokens are not charged to me at all

Steps to Reproduce

create a plan with your loved model (i did with opus)
build that plan with composer

Expected Behavior

it should count the input tokens correctly

Screenshots / Screen Recordings

Screenshot_20260126_225921.png
Screenshot_20260126_225921.png354×273 14.1 KB

Operating System

Linux

Version Information

Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.8.0-90-generic

For AI issues: which model did you use?

composer 1

For AI issues: add Request ID with privacy disabled

a04d6e23-2048-4453-97c3-c24841413753

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. This isn’t actually a bug, it’s expected behavior.

Quick summary:

  • Cache Read is input tokens that were served from cache (over 1M in your case)
  • Input = 0 means all incoming tokens were served from cache, not sent again
  • Caching saves money since cache read is cheaper than normal input

So your 1,186,627 tokens are counted correctly: about ~1.1M from cache + ~57K cache write + ~23K output. Everything is working as intended.