GitHub says Kimi K2.7 Code is now generally available in GitHub Copilot as the first open-weight model offered as a selectable option in the Copilot model picker.
That does not make Copilot a local open-model runner. GitHub says Kimi K2.7 Code is hosted by GitHub on Microsoft Azure. It is rolling out first to Copilot Pro, Pro+, and Max plans, with Business, Enterprise, and additional surfaces expanding over the coming weeks.
The model is billed at provider list pricing under usage-based billing. For Copilot Business and Copilot Enterprise, Kimi K2.7 Code is off by default until administrators enable the policy in Copilot settings.
Open-weight choice now sits inside managed Copilot
The important word is selectable. GitHub is not asking users to bring their own weights, host a local server, or wire a separate coding assistant. It is adding an open-weight model to the same Copilot picker that already routes users among hosted model options.
That makes the open-weight story easier for developers and more bounded for administrators. A user gets another coding model option in familiar Copilot surfaces. An enterprise still gets a policy switch before the model is available to the organization.
GitHub names a broad target surface list: Visual Studio Code, Visual Studio, Copilot CLI, GitHub Copilot cloud agent, GitHub Copilot App, github.com, GitHub Mobile, JetBrains, Xcode, and Eclipse. The rollout is gradual, so the list is an availability direction, not a guarantee that every user sees the model today.
The governance question is not solved by the word open
GitHub’s admin default is cautious. Business and Enterprise administrators must explicitly enable the Kimi K2.7 Code policy before anyone in their organization can select it. GitHub also recommends that administrators review open-weight models against their own security, compliance, and data-governance requirements.
That is the right posture. Open-weight does not automatically mean the hosted service has the same risk profile as local inference. The model may be open-weight, but the Copilot integration is still a hosted product with usage billing, policy controls, and enterprise data-handling questions.
For buyers, the decision is less about ideology and more about fit: code quality on their repositories, latency, price, supported surfaces, data controls, and whether the model behaves well under their secure-development workflows.
