MoonshotAI / MoonshotAI/kimi-code
usage Manipulation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What version of Kimi Code is running?
Latest version.
Which open platform/subscription were you using?
VS Code extension
Which model were you using?
K3
What platform is your computer?
Windows 11.
What issue are you seeing?
It is obvious. I think a lot of people are dealing with this.
What steps can reproduce the bug?
there is a usage manipulation by your company
What is the expected behavior?
to be honest
Additional information
the weekly limit isn't resetting after five hours and it is always used up like 50% before I even sent a first message after 10 hours maybe from the first use. I subscribed to your service in order to save tokens, but you were a big scam. I thought maybe subscribing is better than Claude, but I realized that you are just a trash service
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no files, tests, or entry points. Start by reproducing the usage-limit behavior in the VS Code extension on Windows 11 with the K3 model, then compare the displayed weekly balance before and after the reset period; done means the limit resets as expected and first-use consumption is accurately reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100