haylanandClaude Bot
a0e5e9704b
- CONTEXT.md glossary - README reduced to intro, quickstart and doc index - new architecture.md, gateway.md (from proxy-key-onboarding.md), operations.md; network-access.md rewritten - coding-cli-setup: stale OMNIROUTE_PORT:-4000 endpoint, terms and duplicated per-slot/classifier explanations fixed - research/README.md index; proxy-request-priority.md moved there as superseded Every doc names keys instead of restating values and links its source. Refs #55 (#56, #57, #59, #60) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
693 B
693 B
Kimi CLI
Source of truth: Kimi CLI's repo for config keys; the overview for the gateway endpoint and context size. If this page disagrees with them, they win.
Kimi CLI speaks plain OpenAI Chat Completions. Configure a provider block in its config file (config.toml):
[providers.openai]
type = "openai"
base_url = "http://<server>:<OMNIROUTE_API_PORT>/v1"
api_key = "<kimi-cli API key>"
If Kimi CLI's response parsing gets confused by Qwen's <think>...</think> reasoning tags, check its reasoning_key setting — it's configurable for non-standard local server responses.