GitHub has added Kimi K3 to GitHub Copilot, then temporarily paused the rollout while mitigating an incident with GitHub Actions.
The August 6 changelog says Kimi K3 is an open-weight model hosted by GitHub on Fireworks AI. GitHub says it is beginning to roll out to Copilot Pro, Pro+, Max, Business, and Enterprise plans across Visual Studio Code, Visual Studio, Copilot CLI, Copilot cloud agent, the Copilot app, github.com, GitHub Mobile, JetBrains, Xcode, and Eclipse.
The same page now carries an editor’s note: GitHub temporarily paused the Kimi K3 rollout while it mitigates a GitHub Actions incident. The note says GitHub will resume the rollout as soon as possible and update docs with Kimi K3 pricing of $3 per 1 million input tokens, $15 per 1 million output tokens, and $0.30 per 1 million cached input tokens.
For Copilot Business and Enterprise, Kimi K3 is off by default. Administrators have to enable the Kimi K3 policy in Copilot settings before anyone in the organization can select it.
Model choice now includes rollout risk
The Kimi K3 announcement is part of a larger Copilot shift from one preferred model path to a governed model marketplace. GitHub has recently added multiple third-party and open-weight models, expanded reasoning controls, and moved more Copilot usage into token-aware billing.
That makes the pause as important as the availability notice. A model can be technically available, priced, and listed across every major surface, while still being held behind an incident response decision. Teams that pin agent workflows to a specific model need to track the operational state of the route, not only the model’s benchmark profile.
GitHub’s July 31 deprecation notice adds the other side of that issue. The company says several Copilot models will be deprecated across Copilot Chat, inline edits, ask and agent modes, and code completions on September 1, 2026. Enterprise administrators may need to enable alternative models through model policies before the cutoff.
Enterprise admins own the last mile
For individuals, Kimi K3 will mostly appear as another model picker option once the rollout resumes. For businesses, the admin default is the real control.
The model is open-weight, hosted through GitHub’s infrastructure path, and billed at provider list pricing under usage-based billing. That mix touches security review, data-governance policy, budget controls, and developer experience. Leaving Kimi K3 off by default gives organizations time to decide whether it fits their model policy rather than inheriting it as a silent new route.
