GitHub Copilot just added its first open-weight model — Kimi K2.7 signals a new front in the AI coding tool race

GitHub has made Kimi K2.7 Code, an open-weight model from Moonshot AI, generally available in Copilot for Business and Enterprise plans — the first time an open-weight model has appeared in Copilot's model picker, expanding the choice founders and engineering leads have when standardising on an AI coding tool.

GitHub confirmed on 7 July 2026 that Kimi K2.7 Code — an open-weight model from Moonshot AI, hosted by GitHub on Microsoft Azure — is now generally available inside Copilot for Business and Enterprise customers, having rolled out to Pro plans a week earlier. It’s the first open-weight model to appear as a selectable option in Copilot’s model picker, sitting alongside the closed frontier models from Anthropic, OpenAI, and Google. For Business and Enterprise plans it’s opt-in: administrators have to enable it manually before developers can select it.

This matters less for the specific model and more for what it signals about how the model layer inside AI coding tools is evolving. Copilot, Cursor, and others have spent the past year turning themselves into multi-model platforms rather than single-model products — letting teams pick a model per task, per cost tier, or per data-handling requirement. An open-weight option inside that mix gives engineering teams with strict data-residency or self-hosting requirements a path that wasn’t previously available inside Copilot at all, even if most teams will stick with the default closed models for now.

So what

If your organisation has data-governance or self-hosting requirements that have kept AI coding assistants off the table, this is worth a fresh look — model choice inside these tools is no longer fixed, and an open-weight option changes the calculus for regulated or security-conscious teams. For most commissioning conversations the practical takeaway is simpler: which model runs inside your AI coding tool is now a genuine, changeable decision, not a vendor lock-in. Our custom software development work includes advising on tooling choices as part of a build — get in touch if you want a second opinion.

← All research

More research.

GitHub's Copilot metrics now count OpenCode and Claude Code traffic: who really uses which AI coding tool

On 23 October 2026 GitHub added a per-tool breakdown to the Copilot usage metrics API, so tools such as OpenCode and Claude Code are counted even without editor telemetry. It shows how mixed the AI coding tool stack inside software teams has become.

Read ›

GitHub Copilot retires Claude Opus 5 and GPT-5.6 Terra on 16 November: the model-churn bill for buyers

GitHub has announced that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave every Copilot experience on 16 November 2026. For anyone commissioning AI-assisted development, model retirement is now a monthly event to plan around.

Read ›

GitHub Copilot now benchmarks how 'agent-first' your developers are against your industry

On 22 October 2026 GitHub added opt-in industry comparisons to its Copilot impact dashboard, ranking firms by share of agent-first developers and by the merge rate of agentic pull requests. Here is how to read the numbers when you are buying software.

Read ›

Apple's new bait-and-switch rule 2.5.19: what it means for AI-built and fast-shipped apps

On 16 October 2026 Apple updated its App Review Guidelines: apps that change after approval can be removed from the App Store and the Developer Program, and AI-generated intimate imagery is now explicitly covered. Here is what founders commissioning an iOS app should check.

Read ›

GitHub Copilot agentic autofix is generally available: AI now fixes security alerts, and bills for it

GitHub made agentic autofix for code scanning alerts generally available on 15 October 2026. Copilot can now fix up to 25 security alerts in one pull request, using AI credits your supplier or your team pays for.

Read ›

GitHub AI Scan for pull requests goes GA: AI security checks for PHP, Terraform and Dockerfiles

GitHub's AI Scan for pull requests became generally available on 15 October 2026, checking languages the standard scanner misses. Findings are advisory and cannot block a merge, which matters when you buy software.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work