Usage limits / membership quota depreciate much faster after recent release (affects K3 and K2.7)

What version of Kimi Code is running?

0.29.0

Which open platform/subscription were you using?

Kimi Code membership (weekly quota)

Which model were you using?

kimi-k3 and kimi-k2.7

What platform is your computer?

Linux

What issue are you seeing?

Since the recent release, my membership quota / usage limits depreciate much faster than before for the same kind of work. This is not a case of excessive input/output token volume — token counts in a session look reasonable — but the quota balance itself drops noticeably faster per request/session on both kimi-k3 and kimi-k2.7.

For example, tasks that previously lasted through several sessions now burn through the weekly quota much earlier. The change seemed to coincide with the Kimi K3 launch / recent CLI update.

What is the expected behavior?

Comparable tasks on K2.7 (and earlier releases) consumed a predictable amount of weekly quota. I expect the quota depreciation rate to stay roughly the same unless the membership pricing/deduction model is explicitly changed.

What is the actual behavior?

Weekly quota depletes significantly faster after the recent release, across both K3 and K2.7, with no obvious spike in token usage in the CLI usage panel.

Additional information

• CLI version: 0.29.0
• Platform: Linux
• Models affected: kimi-k3, kimi-k2.7
• Mode: interactive (not necessarily --auto)
• Happy to provide /usage output and /export-debug-zip if helpful.

Start by reproducing the quota depletion on Kimi Code CLI 0.29.0 with kimi-k3 and kimi-k2.7 on Linux, comparing similar interactive tasks and the CLI usage panel. Collect /usage output and an /export-debug-zip, then verify that weekly quota deductions match the expected behavior for comparable token usage.