feat(byok): add Alibaba Token Plan provider#4284
Conversation
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
| 'zhipuai-coding-plan': 'GLM Coding Plan', | ||
|
|
||
| // Alibaba | ||
| 'alibaba-token-plan': 'Alibaba Token Plan', |
There was a problem hiding this comment.
WARNING: This mapping misses the existing Alibaba provider ID
generateByokProvidersNotification() is matching the extension's apiProvider values from notification_byok_providers_jan_19, but the established Alibaba provider ID elsewhere in the app is alibaba and Qwen models normalize into that provider. Adding only alibaba-token-plan means existing Alibaba users will not match this lookup, so the new BYOK notification will never reach the users it is meant to target.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Previous Review Summary (commit 1b78998)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 1b78998)Status: 1 Issue Found | Recommendation: Address before merge Fix these issues in Kilo Cloud Overview
Issue Details (click to expand)WARNING
Files Reviewed (7 files)
Reviewed by gpt-5.4-2026-03-05 · Input: 78.1K · Output: 17.3K · Cached: 402.6K Review guidance: REVIEW.md from base branch |
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Summary
Verification
Visual Changes
N/A
Reviewer Notes
The provider follows the existing Xiaomi Token Plan direct-BYOK pattern. Runtime model metadata comes from the
alibaba-token-planentry in models.dev.