[Bug] Token calculation displays corrupted metrics and triggers premature session limits
Bug Description
Critical token calculation & session limit bug (v2.1.206)
Right after my session limit was reset at 2:10 PM (Asia/Seoul), I was instantly hit with another session limit (resets 7:00 PM) without executing a single command or receiving any output.
The status bar showed an abnormal and corrupted token utilization metrics: "세션 : 102% (-> 1912%)". This strongly indicates a massive multiplier calculation error, backend telemetry counter glitch, or an invisible background sub-agent infinite loop burning tokens instantly upon session initialization.
This completely blocks usability. Please investigate the token counting logic regression in this build.Critical token calculation & session limit bug (v2.1.206)
Right after my session limit was reset at 2:10 PM (Asia/Seoul), I was instantly hit with another session limit (resets 7:00 PM) without executing a single command or receiving any output.
The status bar showed an abnormal and corrupted token utilization metrics: "세션 : 102% (-> 1912%)". This strongly indicates a massive multiplier calculation error, backend telemetry counter glitch, or an invisible background sub-agent infinite loop burning tokens instantly upon session initialization.
This completely blocks usability. Please investigate the token counting logic regression in this build.
Environment Info
- Platform: darwin
- Terminal: xterm-256color
- Version: 2.1.206
- Feedback ID: 6d7a576b-3580-4201-b8a4-2d10a3f0bb9d
Errors
[]