omk doctor: false warnings when custom provider configured via config.toml

[aliatx2017]

Problem

omk doctor shows false-positive warnings when kimi CLI is configured with a custom provider (e.g. OpenAI-compatible endpoint) instead of native Moonshot auth:

• "Kimi Session — kimi login may be required"
• "Kimi Config — ~/.kimi/config.toml missing"
• "Kimi Web Tools — web search tools not detected"

These are all Moonshot-native assumptions. A valid custom config.toml makes them incorrect.

Verified Working Config

kimi CLI v1.43.0 supports custom providers via ~/.kimi/config.toml:

default_model = "kimi26"
default_thinking = true

[providers.ollama]
type = "openai_legacy"
base_url = "https://ollama.com/v1"
api_key = "your-key"

[models.kimi26]
provider = "ollama"
model = "kimi-k2.6"
max_context_size = 256000
capabilities = ["thinking", "image_in"]

Test command:

kimi --config-file ~/.kimi/config.toml --print -p 'say hi' --thinking --model kimi26

Response received: 25,308 input / 35 output tokens. No kimi login required.

Suggested Fix

1. omk doctor Kimi section: detect non-Moonshot providers in config, suppress login/web-tool warnings
2. omk provider doctor: extend beyond DeepSeek to test custom endpoint reachability
3. Docs: add "Custom OpenAI-compatible provider" section

Env

• OMK v1.1.13
• kimi-cli v1.43.0
• Provider type: openai_legacy via config.toml
• OS: macOS 26.5 / Apple Silicon

[aliatx2017]

Update: resolved all doctor warnings via config + manual fixes. Summary:

Warning	Fix
Kimi Session/Config missing	~/.kimi/config.toml with custom openai_legacy provider
Agent YAML Tools	Add explicit tools: block to .omk/agents/root.yaml
Global MCP missing	OMK_MCP_ALLOW_WRITE_CONFIG=1 omk sync --global — manual file creation insufficient
Global Memory missing	Same sync command
OMK Hooks persistent	Add # >>> omk managed hooks marker to ~/.kimi/config.toml, then sync

Important: OMK_MCP_ALLOW_WRITE_CONFIG=1 required. Without it, omk sync --global skips ~/.kimi/ writes silently.

Remaining: ℹ️ Kimi Web Tools (info-level only, not ⚠️ warning) + Git dirty. Both cosmetic.

All green now.

[dmae97]

I have reviewed the issue. The detailed environment configuration and your workaround process are well noted.

As you pointed out, the current validation logic of omk doctor is tightly coupled with the default Moonshot native environment. The false positives occurring when using custom providers (like openai_legacy) are a known architectural limitation that needs to be addressed.

Based on your suggestions and the manual fixes you provided, I will proceed with the following updates:

omk doctor Logic Update: Modify the logic to parse ~/.kimi/config.toml. If a non-Moonshot provider is detected as the default, it will suppress unnecessary login and web-tool warnings.

omk provider doctor Extension: Extend the reachability test to support custom endpoint pinging.

Fix Silent Skip on Sync: The silent skipping of write operations when OMK_MCP_ALLOW_WRITE_CONFIG=1 is not set is a UX flaw. I will patch omk sync --global to output explicit warnings when it skips writes due to lack of permission.

Documentation: Add a dedicated "Custom OpenAI-compatible provider" section to the documentation.

For now, the workarounds you have documented are the correct and optimal approach for v1.1.13. I will track these changes and update this thread once the fixes are merged.