Kimi K3

At a glance

What Kimi K3 does

Vision, Tool use, Function calling, Long-context retrieval, Agentic tooling, MoE

Best for

Agentic coding at low cost, ultra-long context, China-region deployments

Works well with

Conflicts & caveats

• Trae's built-in model menu may not include Kimi K3 — Trae primarily ships with Claude/GPT/Gemini/DeepSeek.
• Google Antigravity is built around Gemini 3 Pro; Claude and recent GPT-5 models also work, but Kimi K3 is not in the supported model list.
• Kiro's spec mode is tuned for Claude models — Kimi K3 may work but spec-driven flows are best with Claude.
• OpenAI Codex (VS Code) is tied to OpenAI's GPT-5.1 Codex family — Kimi K3 is not selectable inside this integration.
• Gemini CLI is locked to Google Gemini models — your LLM is Kimi K3.
• Privacy conflict: Self-hosted Kimi K3 sends code to cloud @codebase (Cursor). Use local context (Continue indexing, ChromaDB, LanceDB, pgvector, Vespa self-hosted) for true privacy.
• Claude Code only works with Claude models — your LLM is Kimi K3.
• Devin uses Cognition's proprietary model internally — your selected Kimi K3 will be ignored.
• OpenAI Codex (Cloud) runs GPT-5.1 Codex internally — your selected Kimi K3 will be ignored.
• Jules runs Gemini models internally — your selected Kimi K3 will be ignored.
• The Claude Code SDK is tuned for Claude models — Kimi K3 may work via the model adapter but loses Claude-specific features (thinking, prompt caching, sub-agents).
• Lovable uses a fixed internal model — your selected Kimi K3 will be ignored.
• Replit Agent 3 uses its own model selection internally — your selected Kimi K3 will be ignored.