Problem or Use Case
Kimi / Moonshot has separate keys and API endpoints for China vs international users. With only one kimi-coding path, it’s easy to use the wrong key or base URL and get auth errors. Users need a clear, first-class way to select the China region in Hermes (CLI, config, and docs).
Proposed Solution
- Add a dedicated provider id kimi-coding-cn (with short aliases if we already support them).
- Use KIMI_CN_API_KEY and default base https://api.moonshot.cn/v1, and document how this differs from kimi-coding + KIMI_API_KEY.
- Expose it everywhere users pick providers: hermes chat --provider, interactive model/provider flow, and env docs (e.g. HERMES_INFERENCE_PROVIDER).
- Update provider docs (e.g. providers.md, env vars, quickstart/config snippets) so China vs international setup is obvious.
Alternatives Considered
No response
Feature Type
Performance / reliability
Scope
Medium (few files, < 300 lines)
Contribution
Problem or Use Case
Kimi / Moonshot has separate keys and API endpoints for China vs international users. With only one kimi-coding path, it’s easy to use the wrong key or base URL and get auth errors. Users need a clear, first-class way to select the China region in Hermes (CLI, config, and docs).
Proposed Solution
Alternatives Considered
No response
Feature Type
Performance / reliability
Scope
Medium (few files, < 300 lines)
Contribution