Kimi K3 and Kimi K2.7 Code can both appear in developer workflows, but they should not be treated as interchangeable labels.
Start with the integration surface
If your tool officially lists a Kimi model, use the model name and support status from that tool first. Cursor, gateways, command-line agents, and direct API calls may expose different model choices.
For direct API work, use the model names documented by Kimi. For tool integrations, confirm whether the tool is sending requests to Kimi directly, through a gateway, or through its own backend.
Choose by workload shape
Use Kimi K3 when your priority is a Kimi K3 API workflow, long-context planning, cost modeling, and endpoints documented for Kimi K3.
Use Kimi K2.7 Code when a coding tool or official model list explicitly supports that model and you want the most predictable integration inside that tool.
Avoid accidental model drift
Model drift happens when a UI label, gateway alias, and provider model name do not match. Always verify usage in logs or provider dashboards.
If you are comparing results, keep prompts, context size, output limits, and temperature consistent. Otherwise you may compare tool settings rather than the models themselves.