Repository navigation
feat: support kimi coding plan monthly quota (limit_month_total/code) parsing, display, and 429 cooldown - #7856
Conversation
… parsing, display, and 429 cooldown Co-authored-by: Randark-JMT <56223739+Randark-JMT@users.noreply.github.com>
|
经过检查,CI 测试失败并非代码问题,而是 DNS 解析超时问题 |
|
This looks good to me at a glance — thanks for putting it together. |
|
@Wei-Shaw Could you take a quick look when you have a moment? Thanks! |
|
Thanks for working on Kimi monthly quotas. I reproduced the underlying issue on v0.2.18: the upstream I am preparing a focused follow-up against current main, with parser, snapshot, scheduling and frontend regression coverage, crediting this PR. I will link it here so the work can be reused or incorporated into this PR; I am not asking for this PR to be closed. I also inspected the failed CI job: |
|
The current-main follow-up is now available as #8347 (draft while CI is running), with attribution to this PR. It adds per-window legacy fallbacks, preserves the selected monthly window reset, and tests snapshot persistence plus manual UI refresh. Happy for the patch to be incorporated here instead if preferred. No request to close this PR. |
|
@davidche1116 I'm glad you noticed this PR and are willing to credit my contribution in yours! Based on my observation, Wei-Shaw seems to be using an automated AI agent to review PRs, which tends to ignore older ones. For my PR that has been pending for a long time, there seems to be little hope of getting noticed and reviewed by Wei-Shaw. I really hope your PR gets noticed and merged into the main branch! Thanks again for leaving a comment on this PR!🤗 |
|
Thank you for the kind words, and especially for doing the original work on Kimi monthly quotas! Your PR helped identify the missing support, so crediting your contribution was the right thing to do. 🤗 The follow-up in #8347 is now ready for review. The full CI and security checks have passed in my fork on the exact PR commit, including backend unit and integration tests, and the CLA check has passed too. The upstream workflows are still awaiting maintainer approval. I hope the updated patch and regression tests make it easier to review and get this support into an official release. Thanks again for laying the groundwork—happy to collaborate on any feedback that comes back! |
Support current usage ratios alongside per-window legacy fallbacks, preserve monthly reset semantics, and include Kimi monthly snapshots in existing scheduling checks. Add quota persistence and manual-refresh regressions. Follow-up to Wei-Shaw#7856.
This pull request adds comprehensive support for Kimi's new monthly plan quota reporting, including backend logic for parsing, evaluating, and snapshotting monthly quota tiers, as well as frontend display and testing. The changes ensure that monthly quota limits are correctly handled for both logic and UI, alongside existing 5h and weekly windows.
Backend: Kimi monthly quota support
limit_month_totalandlimit_month_codefrom API responses, taking the higher usage ratio and the earlier reset time.Backend: Tests
Frontend: UI and tests
purple), matching the new backend logic, and added tests to verify correct rendering and color coding for monthly plans. [1] [2] [3] [4]Documentation and comments
These changes ensure robust, accurate handling and display of Kimi's quota plans, especially for the new monthly-based limits.