GitHub adds Gemini 4 Carbon to Copilot for four paid plans
The model targets complex coding and security-focused work. Access is gradual, usage is metered, and workplace administrators can control availability.
Loading page…
The model targets complex coding and security-focused work. Access is gradual, usage is metered, and workplace administrators can control availability.
Listen to this story
GitHub has added Google’s Gemini 4 Carbon to Copilot, giving paid subscribers another model option for coding and security-oriented tasks inside their existing development workflow. The addition broadens Copilot’s model choice, but access depends on the account’s rollout status and, for workplace plans, administrator policies. Carbon usage is billed separately at provider list pricing under usage-based billing, so plan eligibility does not mean its use is included without additional charges.
Access is for Copilot Pro+, Max, Business and Enterprise subscribers; the rollout may take time to reach every eligible account.
Carbon can be selected in Copilot’s model picker across IDEs, CLI, GitHub’s coding agent, web and mobile.
New models are enabled by default unless an administrator has changed the default or disabled Carbon.
Developers using GitHub Copilot are getting another model choice for complex coding and security-focused work, without leaving their existing development tools. GitHub announced general availability of Google’s Gemini 4 Carbon on November 10, 2026. Access covers four paid plans, but a gradual rollout means eligible subscribers may not see it immediately.
GitHub describes Carbon as designed for complex coding, reasoning and tasks involving AI agents, with an emphasis on secure code generation and security-focused work. That is the company’s description of the model’s intended role, not a quantified claim about how much safer its code will be.
The eligible subscriptions are Copilot Pro+, Max, Business and Enterprise. Users select Carbon through Copilot’s model picker, rather than through a separate Carbon application. GitHub lists availability across editor-based development, command-line work, its coding agent and apps:
General availability does not mean simultaneous access across every eligible account. GitHub tells users who cannot yet find Carbon to check back as the rollout progresses. Subscription eligibility and the model’s appearance in the picker are therefore separate practical checks.
Business and Enterprise administrators can manage Carbon through the model policy in Copilot settings. Those controls let an organization decide whether the model is available to its teams. An eligible workplace subscription alone does not override an administrator’s decision to disable it.
Carbon is billed at provider list pricing under usage-based billing. GitHub directs users to its Copilot models-and-pricing documentation for the details. The eligible-plan list establishes who can access the model; the billing terms separately establish how its use is charged.
Loading discussion...
Join the conversation
Explain whether immediate access or explicit approval should be the default.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.