Skip to main content
AI News

Kimi K3 Reaches GitHub Copilot: Check Plan Access, Model Policy, and Usage Billing

Kimi K3 is rolling out across eligible Copilot plans, so individuals need to check access and billing while organizations must first control policy and governance.

ENHE AI5 min13 views

GitHub announced on August 6, 2026 that Kimi K3 is gradually rolling out to Copilot Pro, Pro+, Max, Business, and Enterprise plans. Eligible users can select it in places such as Visual Studio Code, Copilot CLI, GitHub, and supported IDEs, but availability depends on plan, client, and rollout status. GitHub says Kimi K3 uses provider list pricing under usage-based billing. Business and Enterprise administrators must enable the Kimi K3 policy before members can use it and should review open-weight model governance. For ordinary users, the practical first step is a bounded non-production test with a recorded budget, permissions, changes, tests, and human review rather than an immediate production rollout.

More topic tags (10)
AI NewsAuto PublishingGitHub CopilotAI credits开放权重模型Kimi K3GitHub Copilot Kimi K3Kimi K3 CopilotVS Code AI编程模型选型
Kimi K3 Reaches GitHub Copilot: Check Plan Access, Model Policy, and Usage Billing

Key takeaways

GitHub announced the gradual Kimi K3 rollout to several Copilot plans on August 6, 2026.
The model can be selected in VS Code, Copilot CLI, github.com, and other supported entry points when the account is eligible.
Kimi K3 uses usage-based billing, and Business or Enterprise requires an administrator policy switch.
A first trial should have a non-production boundary, budget, permission record, tests, and human review.

# Kimi K3 Reaches GitHub Copilot: Check Plan Access, Model Policy, and Usage Billing

Published: August 7, 2026

Table of contents

  • Direct answer
  • Fact sources
  • Action steps
  • Why it matters
  • Impact for ordinary AI users
  • Related tools and tutorials
  • FAQ
  • Source links

Direct answer

Kimi K3 is entering GitHub Copilot, but it will not appear for every account at the same time. First check the model picker, plan, rollout status, and usage billing. If a Business or Enterprise user cannot see it, an administrator must check the Kimi K3 policy. Start with a reviewable task in a non-production repository; do not connect a newly available model directly to real secrets, customer data, or automatic merge workflows.

Fact sources

GitHub's August 6, 2026 changelog says the open-weight Kimi K3 model is gradually rolling out to Copilot Pro, Pro+, Max, Business, and Enterprise. GitHub explicitly says the rollout is gradual, so users who do not see the model should check again later.

The announcement lists model-picker access in Visual Studio Code, Visual Studio, Copilot CLI, the GitHub Copilot cloud agent, the Copilot app, github.com, GitHub Mobile, JetBrains, Xcode, and Eclipse. The actual entry point still depends on client version, account plan, and rollout state.

GitHub says Kimi K3 is billed under usage-based billing at provider list pricing. It is off by default for Copilot Business and Enterprise: administrators must enable its policy and should review open-weight models against their own security, compliance, and data-governance requirements.

Kimi's own documentation positions Kimi K3 for long-horizon coding, knowledge work, and reasoning, with a 1M-token context window, tool use, and an OpenAI-compatible API. Those capabilities do not remove the need for permission checks, testing, or human review in Copilot workflows.

Six steps for a first Kimi K3 test in Copilot

  1. Check whether Kimi K3 appears in the model picker in VS Code, Copilot CLI, or github.com. Do not use an unofficial workaround if the gradual rollout has not reached the account.
  2. Review the current Copilot plan and usage-based billing settings, then record a trial credit or budget ceiling before experimenting.
  3. For Business or Enterprise, ask an administrator to confirm the Kimi K3 policy, organization data rules, and permitted scope before enabling access.
  4. Start from a sample repository with no customer data, secrets, or production configuration and use one task that a human can accept or reject.
  5. Keep the prompt, model choice, file changes, commands, and test result. A new model name is not a reason to skip code review.
  6. Expand only after quality, cost, permissions, and rollback behavior are understood for the real workflow.

Why it matters

Kimi K3 in Copilot moves model selection from a separate platform decision into an account, policy, and cost decision inside the everyday coding entry point. Individuals need to know whether it is available, how it is billed, and whether the output is reliable. Teams need model policy, data boundaries, logs, budgets, and human review before broad enablement.

Impact for ordinary AI users

People using AI for coding, technical research, or debugging can treat Kimi K3 as one comparable Copilot option, not an automatic replacement for existing models. The lower-risk approach is to compare the same non-sensitive sample task and its rework level before retaining the model. Organizations should keep a reversible pilot boundary instead of treating an administrator policy as a one-time checkbox.

Related tools and tutorials

ENHE's Kimi K3 versus Qwen3.8-Max guide, Kimi K2.7 Code in Copilot explanation, safe Copilot CLI trial guide, and its software, account-services, and skill-learning sections can support model choice, permissions, budget, and testing work.

Kimi K3 versus Qwen3.8-Max model guide;Kimi K2.7 Code in Copilot explainer;Safe Copilot CLI trial guide;AI software and tool entry points;AI account permissions and cost services;AI skill tutorials and validation methods

FAQ

Why do I not see Kimi K3 in Copilot yet?

GitHub says the model is rolling out gradually to eligible plans. Check the plan, client, and model picker; Business and Enterprise also require an administrator to enable the Kimi K3 policy.

Is Kimi K3 free in Copilot?

GitHub says it is billed under usage-based billing at provider list pricing. Use the current in-account Copilot pricing and budget settings instead of screenshots or third-party estimates.

Can I use it directly on a production repository?

Do not start there. First verify output, tool permissions, tests, and human review in a non-production repository, then decide whether to broaden the scope.

Source links

  • GitHub Changelog: Kimi K3 is now available in GitHub Copilot (2026-08-06)
  • GitHub Docs: Supported AI models in GitHub Copilot
  • GitHub Copilot plans and pricing
  • Kimi API开放平台:Kimi K3模型介绍

What this means for everyday users

For ENHE users, the useful action is not chasing a model name. Put plan access, usage billing, organization policy, data scope, test records, and rollback into one trial checklist.

Related reading

Gemini 4 Hydrogen Launches: Map Surfaces, Thinking Levels, and Task Cost Before Switching

Google released Gemini 4 Hydrogen on November 12, 2026 as a fast model for everyday and agentic work. It offers low, medium, high, and xhigh thinking levels and is rolling out across the Gemini app, Search, AI Studio, the Gemini API, Gemini for business, Antigravity, and eligible Google Sheets subscriptions. Those surfaces do not share one entitlement or one billing path. This article provides a selection map built around surface, account, task, input, expected output, and fallback. It recommends testing one inspectable document or spreadsheet task at two thinking levels, measuring corrections and total token cost, and keeping the previous workflow available. Vendor benchmarks remain source claims, not proof of local performance.

GitHub Copilot Enters Xcode’s Built-In Assistant Preview: Should You Switch From the Extension?

GitHub announced on 2026-11-04 that Copilot is available in Xcode’s built-in coding assistant as a public preview starting with Xcode 27.3 beta. The setup requires a Mac running macOS Tahoe 26.6 or later, and GitHub says all Copilot plans are supported. The existing GitHub Copilot for Xcode extension remains a separate option, so this is a workflow choice rather than a forced migration. This guide provides a bounded comparison: verify the beta environment, run the same small coding task in the current extension and built-in assistant, compare context, edits, permission prompts, tests, and recovery, then keep the route that produces the clearest reviewable evidence.

GitHub Copilot SDK Is Becoming Microsoft Copilot SDK: What Existing Projects Should Change Now

GitHub says GitHub Copilot SDK will transition in phases to Microsoft Copilot SDK, creating a shared agent foundation across Microsoft and GitHub products while applications retain control of prompts, tools, policies, and their own experience. Existing users do not need to make immediate changes, and current packages, namespaces, or documentation may still use the old name during the transition. This guide turns the announcement into a practical migration-readiness checklist: inventory dependencies, record authentication and billing assumptions, preserve behavioral baselines, monitor official package guidance, and rehearse rollback before changing production code. It does not claim a completed package migration or a universal release date.

GitHub Copilot Projects Preview: Keep Human Acceptance Across Multi-Repository Work

GitHub announced Copilot Projects in public preview on October 28, 2026. A project can combine multiple repositories, design mocks, Slack threads, and meeting notes, then coordinate as many agents as needed and return results such as pull requests for review. Project automations can repeat work when a trigger occurs. That broader context is useful for features that span code and design, but it also makes acceptance criteria and tool permissions more important. This article provides a small multi-repository trial template with defined inputs, allowed tools, expected artifacts, stop conditions, and human acceptance so an agent result is not mistaken for completed work.

VS Code Agent Host Runs in the Background: Choose Phone Control, Local Machines, or Cloud Sessions

GitHub announced its VS Code Copilot Universe release on October 28, 2026. The new Agent Host lets sessions continue after a project folder or editor window closes, can run on another machine through Remote SSH or dev tunnels, and can be directed from GitHub Mobile. A local or remote machine and its Agent Host must remain running when the work executes there. Computer use is experimental and requires approval for each application. The open Agent Host Protocol lets custom clients reconnect to the same live session. This article compares local, remote, and cloud placement, then provides a first-run checklist for availability, permissions, desktop access, and recovery.

What Is Replica? A Validation Guide for AI Prototypes Built From Your Design System

Replica is an open-source AI prototyping tool released by GitHub Design on October 28, 2026. It uses a team’s existing components, patterns, and documentation to guide interactive prototypes instead of starting from a generic visual language. Team members can describe and refine a prototype through the GitHub Copilot app, begin locally, and optionally deploy a self-hosted Replica Hub for review and comments. The project is available under the MIT license. This durable guide explains the required design-system inputs, a small example task, expected outputs, consistency checks, feedback handling, and failure recovery so a prototype can inform product discussion without being presented as production code or a tested interface.

Summary

Kimi K3 becoming available in GitHub Copilot is a real new model-access event, but first it is an account, policy, and billing decision. Confirm rollout, plan, model policy, and budget, then test a non-sensitive task with human review before making it part of a controlled workflow.