Kimi K2.7 Code Now Generally Available in GitHub Copilot

Release Details

Kimi K2.7 Code reached general availability in GitHub Copilot on July 1, 2026. GitHub added the open-weight model as a selectable option in the model picker, marking the first time an open-weight model appears alongside proprietary ones. The model runs on Microsoft Azure infrastructure and uses usage-based billing at provider list pricing. Initial access covers Copilot Pro, Pro+, and Max plans, with gradual rollout to Business and Enterprise tiers.

Access Across Development Environments

Users can select Kimi K2.7 Code in Visual Studio Code 1.127.0 and later, Visual Studio 17.14.6 and later, JetBrains 1.9.1-251 and later, plus Xcode and Eclipse. Command-line access works through Copilot CLI, while web and mobile surfaces include github.com, the GitHub Copilot cloud agent, and the GitHub Mobile apps on iOS and Android. Administrators enable the model through a dedicated policy toggle in Copilot settings for Business and Enterprise organizations. Without the policy active, the option remains hidden from all team members.

Pricing Structure and Model Trade-offs

Billing follows the provider's list rates under usage-based metering rather than flat subscription add-ons. This setup gives developers a lower-cost alternative when token volume stays moderate. Open-weight models like Kimi K2.7 Code expose weights for inspection, which can matter for teams running internal audits. In exchange, performance on certain coding tasks may vary compared with closed models that receive continuous fine-tuning on proprietary data. GitHub routes requests to the chosen model without additional client configuration once selected in the picker.

Policy Controls for Organizations

Enterprise administrators must explicitly enable the Kimi K2.7 Code policy before any user can pick the model. The default state keeps the model disabled, requiring a deliberate decision that accounts for data residency and compliance rules. GitHub recommends reviewing open-weight models against internal security standards before activation. Once enabled, individual developers retain the choice in the model picker, but the organization retains the override capability through the same policy setting.

Practical Considerations When Switching Models

Switching to Kimi K2.7 Code requires no code changes in existing projects. The model accepts the same prompt formats used with other Copilot models. Teams tracking request costs should monitor usage dashboards, since per-token pricing differs from included quota models. Rollout monitoring continues, so availability in additional surfaces may appear in subsequent updates without further configuration.

FAQs

Does Kimi K2.7 Code require separate installation? No. The model appears in the existing Copilot model picker once the rollout reaches the user's plan and IDE version.

Can Copilot Business users access it immediately? Access stays disabled until an administrator turns on the specific policy in organization settings.

How does billing differ from standard Copilot plans? Requests to Kimi K2.7 Code incur separate usage charges at the provider's published rates instead of drawing from the base plan quota.

---

📖 Related articles

• Agentic Coding: Una Trappola per lo Sviluppo Software?
• File agents.md: utili per gli agenti di coding?
• Lean-ctx: Ottimizzatore Ibrido Riduce Consumo Token LLM del 89-99%