Configuration is too complex

[Charles-ux-bit]

I want to use kimi as backend, however, I found it very difficult to override the default config setting ( anthropic ). Can you provide some simple ways? Thanks a lot.

[tjb-tech]

Thanks for the feedback — this is fair. The current provider/profile/auth setup is flexible, but it can feel too complex when the goal is simply "I want to use Kimi".\n\nToday, the shortest path is usually to pick one of the built-in Kimi profiles directly (for example kimi-anthropic or moonshot) and then log in to that profile, instead of trying to reason from the default Anthropic configuration outward.\n\nWe agree the onboarding here can be simpler. We will keep looking at ways to make provider setup more direct, especially for common backends like Kimi, so users do not need to understand as much of the underlying profile/config machinery up front.

[tjb-tech]

This looks addressed by the current provider workflow UX.

The configuration flow is no longer the old auth -> provider -> model path. Current OpenHarness uses workflow-oriented setup via:

• oh setup
• oh provider list
• oh provider use <profile>

Kimi is supported through the Anthropic-compatible/OpenAI-compatible workflow model rather than requiring manual override of the default Anthropic config.

In the current docs:

• README.md documents oh setup
• provider workflows are described explicitly under Anthropic-Compatible API and OpenAI-Compatible API
• the Chinese README also documents the same workflow and Kimi/OpenRouter examples

So the original usability gap here has effectively been addressed by the newer setup/profile flow.