GitHub adds Gemini 4 Neon to Copilot, with a lower-cost pitch from Google
Google claims quality close to Carbon with faster responses and fewer unwanted coding changes. Usage is metered, and eligible accounts will gain access gradually.
Loading page…
Google claims quality close to Carbon with faster responses and fewer unwanted coding changes. Usage is metered, and eligible accounts will gain access gradually.
Listen to this story
GitHub’s November 18, 2026, Copilot release adds Gemini 4 Neon as a selectable option across coding editors, the CLI, its coding agent, web and mobile, with access rolling out gradually. Google positions Neon as close to Gemini 4 Carbon in quality while using fewer tokens per task, responding faster and making fewer unwanted or unsupported coding claims. GitHub does not quantify savings or independently validate those performance claims; billing is at provider list pricing. Business and Enterprise access may be enabled automatically under GitHub’s default model policy unless administrators changed the settings.
Neon is available to Copilot Pro+, Max, Business and Enterprise subscribers through Copilot’s model picker.
Supported surfaces include Visual Studio Code, Visual Studio, JetBrains IDEs, Xcode, Eclipse, Copilot CLI, GitHub’s coding agent and app, github.com, and GitHub Mobile.
Business and Enterprise administrators can manage Neon through Copilot’s model policy; existing settings determine whether it is enabled automatically.
Developers using GitHub Copilot have a new model option pitched at getting coding work done with less cost and fewer unwanted edits. GitHub made Gemini 4 Neon generally available on November 18, 2026, for four paid plans. Access is gradual, and the performance claims come from Google.
GitHub describes Neon as designed for coding carried out by AI agents, multistep tool use and knowledge work. Its announcement presents the comparison with Gemini 4 Carbon as an efficiency argument: Google says Neon delivers quality close to Carbon at a lower token cost per task.
The claimed differences extend beyond cost. Google says Neon starts responding faster than Carbon and makes fewer coding changes that users did not request. It also says Neon is less likely to make unsupported claims about code, tools or test results. Those are Google's assessments, not independent findings presented in the announcement.
Neon is available to Copilot Pro+, Max, Business and Enterprise users. Eligible users select it through Copilot's model picker, rather than a separate Neon application. GitHub lists support across editor-based coding, command-line work, its coding agent, and web and mobile interfaces:
That is the supported reach of the release, not a promise that every eligible account already has the option. GitHub says users who do not see Neon should check again as the rollout progresses.
Business and Enterprise administrators can manage Neon through the model policy in Copilot settings. Under GitHub's default model enablement, new models are automatically enabled unless an administrator has turned off the global default or explicitly disabled this model.
For workplace users, a new model therefore does not necessarily require a new approval. Existing administrator settings determine whether Neon becomes available automatically as the rollout reaches their accounts.
Loading discussion...
Join the conversation
Explain whether immediate access or approval first should be the default.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.