When configuring the Kimi provider in Hermes, the auto-discovered model name k2p6 (shown in the dropdown/model list) does not match the actual model ID expected by the Moonshot API (kimi-k2.6). This causes all API requests to fail with a model-not-found error. 4. Actual: Connection fails / model not found error.

TL;DR

Update the model display name to API model ID mapping for the Kimi provider to correctly map k2p6 to kimi-k2.6.

Guidance

• Verify the model mapping configuration for the Kimi provider to ensure that k2p6 is correctly mapped to kimi-k2.6.
• Check if there are any existing mapping overrides or custom configurations that may be causing the mismatch.
• Consider updating the auto-discovery logic to correctly handle the model name formatting for the Kimi provider.
• Test the workaround of manually typing kimi-k2.6 as the model name to confirm that it resolves the issue.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The issue seems to be specific to the Kimi provider and the k2p6 model, so any changes should be carefully tested to ensure they do not introduce issues with other providers or models.

Recommendation

Apply workaround: Manually type kimi-k2.6 as the model name instead of using the dropdown, until a permanent fix for the model mapping can be implemented. This is because the workaround has been confirmed to work and allows for continued use of the API while a more permanent solution is developed.