#6015: CLI: clarify Moonshot AI/Kimi auth option labels based on user feedback
commands
Cluster:
Kimi Model Enhancements
As a Moonshot AI employee, we've received substantial user feedback indicating that the previous hints and labels for selecting Kimi models were confusing. Users had trouble distinguishing between the standard Moonshot API key and the Kimi Code Plan API key.
This commit updates the labels and hints to be more explicit:
- "Moonshot AI" → "Moonshot AI (Kimi K2.5)"
- "Kimi K2 + Kimi Coding" → "API key + Kimi Code Plan"
- "Moonshot AI API key" → "Kimi API key"
- "Kimi Coding API key" → "Kimi Code Plan API key"
These changes should reduce confusion when users configure their Kimi credentials during onboarding.
<!-- greptile_comment -->
<h2>Greptile Overview</h2>
<h3>Greptile Summary</h3>
This PR updates the CLI onboarding/auth-provider selection copy for Moonshot/Kimi credentials to reduce user confusion. Specifically, it renames the Moonshot group label and hint (to explicitly mention Kimi K2.5 and that it requires an API key plus a Kimi Code Plan), and renames the two underlying options so users can distinguish a standard Kimi API key from a Kimi Code Plan API key. These changes are localized to `src/commands/auth-choice-options.ts`, where auth choice groups and options are assembled for the onboarding UI.
<h3>Confidence Score: 4.5/5</h3>
- This PR is safe to merge; it’s a localized copy change with minimal behavioral impact.
- Only user-facing labels/hints were modified; no identifiers, choice values, or control flow changed. Main risk is copy drift/accuracy over time (e.g., hard-coded model version).
- src/commands/auth-choice-options.ts
<!-- greptile_other_comments_section -->
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
**Context used:**
- Context from `dashboard` - CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8))
- Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=0d0c8278-ef8e-4d6c-ab21-f5527e322f13))
<!-- /greptile_comment -->
Most Similar PRs
#5947: Feature/kimi reasoning support
by zzjj7000 · 2026-02-01
80.5%
#21911: Enable `reasoning: true` for Kimi models
by ighostych · 2026-02-20
78.6%
#6960: feat: Add kimi-coding provider support
by YYW0228 · 2026-02-02
78.1%
#6454: fix: enable reasoning flag for Kimi K2.5 in Moonshot provider (#6451)
by coupclawbot · 2026-02-01
77.7%
#22194: fix(agent) Moonshot/Kimi kimi-k2.5 returns ROLE_UNSPECIFIED
by ShengFuC · 2026-02-20
77.3%
#9024: Fix/Moonshot Provider Issue with kimi-k2-thinking Model Role Mappin...
by fotorpics · 2026-02-04
76.6%
#4459: fix: enable image input for Kimi K2.5 and refresh stale config mode...
by manikv12 · 2026-01-30
76.1%
#14187: fix: add Moonshot AI to non-standard provider detection
by shad0wca7 · 2026-02-11
75.0%
#19281: fix: set supportsDeveloperRole false as default for moonshot provider
by MisterGuy420 · 2026-02-17
73.0%
#15117: feat: add Kimi (Moonshot AI) as web_search provider
by adshine · 2026-02-13
72.1%