Gemini 4 Carbon is Google's new frontier AI model, announced on 28 October 2026, focused on coding, long-running agent tasks and cybersecurity. Google reports strong benchmark results for discovering and patching software flaws, but initial access is restricted to selected cyber defenders. Carbon is not yet generally available in the Gemini app or as a self-service API for all developers, and its stated prices concern the planned wider release.
Verified: 29 October 2026. Primary source: Google's Gemini 4 Carbon announcement by Koray Kavukcuoglu. All benchmark and performance figures below are attributed to Google or its named benchmark providers. RKWS has not independently tested Carbon, reviewed its model weights or validated its security claims.
What is Gemini 4 Carbon?
Gemini 4 Carbon is the next model in Google's Gemini 4 family, following the October release of Gemini 4 Argon. Google positions it for prolonged workflows that involve interpreting complex problems, planning multiple steps, working with code and performing authorized cyberdefense tasks.
The principal difference in the announcement is greater capability in long-horizon work: Google says Carbon can persist through difficult engineering tasks, investigate subtle bugs across a codebase and produce candidate fixes while improving its ability to remain within the user's requested scope.
Its public report does not establish that every organization can access the model immediately, nor does it provide an independently audited guarantee that complex tasks always finish correctly. Access is being phased in deliberately because cybersecurity competence can have both defensive and misuse implications.
How does Gemini 4 Carbon compare with Gemini 4 Argon?
Google says Carbon builds on Argon with higher reported results in coding, software security and instruction following. These are measurements from specified evaluations and should be interpreted as such, not as a blanket declaration that every Argon workflow should immediately switch.
| Dimension | Gemini 4 Argon | Gemini 4 Carbon |
|---|---|---|
| Release timing | Introduced earlier in October 2026 | Announced 28 October 2026 |
| Initial access | Available via specified products and developer channels | Selected cyber defenders initially |
| Emphasis | Broad coding, reasoning and cyberdefense | Long-horizon engineering and advanced cyberdefense |
| Benchmark claims | Earlier baseline and independent evaluations | Higher reported results on several new security tests |
| Practical adoption | Evaluate where available under the current terms | Monitor staged release and assess eligibility |
See our existing Gemini 4 Argon guide for the earlier model's access and limitations. This article focuses specifically on Carbon's new research claims and restricted rollout.
Which cybersecurity benchmarks did Gemini 4 Carbon score highly on?
Google reported three prominent benchmark outcomes covering the defensive life cycle: finding vulnerabilities, assessing whether a problem is exploitable and generating patches.
| Benchmark | Reported Carbon result | What the test examines |
|---|---|---|
| SEC-bench Pro | 88.2% | Finding difficult vulnerabilities in software |
| ExploitGym | 54.8% | Validating exploitation of specified vulnerabilities |
| CWE-bench | 71.0% | Repairing vulnerability root causes in code |
Google notes these external benchmark evaluations were run without deployment guardrails. The results are not an accuracy percentage for all codebases, a penetration-testing success rate for every application or permission to attempt unauthorized tests. Dataset composition, evaluation setup and available tools all matter.
Google also reports that Carbon ranked first at the time of publication on the Artificial Analysis Intelligence Index v5.0 with a score of 59. Rankings can change and should not be confused with independently measured customer outcomes.
What does long-horizon agentic coding mean?
Long-horizon agentic coding means an AI system works through an engineering goal that needs many coordinated actions: inspecting files, considering alternatives, writing changes, testing, and revisiting an earlier assumption. It is different from asking a chatbot for one code snippet.
Google describes internal runs lasting for days to investigate low-level system behavior and difficult software defects. That description is evidence of an intended capability, not proof that a typical user should allow unrestricted autonomous execution for days on a production server.
- Define one engineering goal and its measurable acceptance test.
- Give the agent a clean repository or sandbox, not production credentials.
- Allow code analysis and controlled tests within stated resource limits.
- Require the agent to document assumptions, changes and uncertain findings.
- Review candidate patches and rerun independent regression and security checks.
- Approve merge and deployment through normal engineering controls.
Our AI coding agents and developer responsibilities article explores why specification, verification and release ownership remain human jobs.
How has Google measured improvements in model behavior?
Beyond raw performance, Google says Carbon reduced excessive actions and incomplete execution in its internal evaluations. It reported 26% less overreach and 29% less under-service relative to the stated evaluation baseline. These terms concern scope adherence, not universal reductions in live production incidents.
Google also reported a 0.0% successful-attack rate for Carbon on the evaluated Gray Swan indirect prompt-injection benchmark. A zero on one finite test set does not mean the model is immune to all prompt injection. New attacks, different tool environments and more complex workflows can still create risks.
For a defensive implementation, see our prompt-injection permissions checklist. Independent policy enforcement remains essential even when the model behaves more safely in a benchmark.
What is the Gemini 4 Carbon rollout and who can access it?
Carbon is initially being made available to a subset of cyber defenders. Google says it will gradually add trusted partners through its Fairwind Program while it evaluates safeguards and collects feedback. Google also described participation in a voluntary US government pre-release testing process.
Developers, businesses and consumers are expected to receive broader access later, but Google did not establish one universal public release date in the 28 October announcement. A developer in India should not claim production API access without verifying that the model has actually been enabled for the intended account, product and region.
Enterprises planning to use Carbon should monitor Google's product release notes and check data-processing terms, usage policies, quotas, model identifiers and appropriate legal authorizations before an integration project.
What pricing did Google announce for Gemini 4 Carbon?
Google published the following planned public-facing prices: $2 per million input tokens and $10 per million output tokens at introductory rates. It also said cached input would be priced at a 95% discount relative to regular input. After the introductory period, Google lists $4 per million input tokens and $20 per million output tokens.
| Pricing phase | Input / 1M tokens | Output / 1M tokens |
|---|---|---|
| Announced introductory pricing | $2 | $10 |
| Announced later pricing | $4 | $20 |
| Cached-input discount | 95% off stated input price when applicable | Not the same as an output discount |
Because general developer access had not launched on 28 October, these figures are announced terms rather than evidence of a currently billable public API for everyone. Confirm the actual rates and billing conditions when the service becomes available to your account.
Could Gemini 4 Carbon help Indian software teams?
Potential uses include examining complex internal repositories, summarizing findings from authorized security scans, supporting patch development and helping analyze challenging technical errors. The benefit depends on whether a team's real workload and security model match the product's strengths.
- Web development: isolate hard-to-reproduce bugs and suggest regression tests
- Cybersecurity: support permitted vulnerability triage and patch review
- Enterprise IT: reason across approved architecture notes and incident histories
- Software quality: evaluate whether a proposed fix solves the original problem without introducing new ones
These are candidate applications, not verified RKWS case studies. High-impact security and software changes should be reviewed and tested by qualified personnel.
What should teams prepare before broad availability?
A practical readiness checklist focuses on evaluation data and access controls, not marketing claims.
- Inventory the coding or security tasks that currently consume the most specialist time.
- Prepare a set of authorized historical cases with known outcomes.
- Measure the current baseline: correctness, time spent, false positives and developer review effort.
- Define sandbox boundaries, restricted tools and permitted data sources.
- Design a human review and escalation process for potentially dangerous operations.
- Reassess the product only after pricing, service terms and actual access are confirmed.
For an operational framework, read AI agent governance in production and AI agent monitoring and observability.
Frequently asked questions about Gemini 4 Carbon
Can I use Gemini 4 Carbon in the Gemini app today?
Google's 28 October announcement does not describe a general consumer launch. Initial access is limited to selected cyber defenders.
Is Carbon better than Argon for cybersecurity?
Google reports higher results on named coding and security evaluations, but results may differ for actual projects and controlled deployment environments.
What benchmark percentages were reported?
88.2% on SEC-bench Pro, 54.8% on ExploitGym and 71.0% on CWE-bench under their stated test conditions.
Does a zero prompt-injection score guarantee security?
No. It describes one tested benchmark. Real agents still require strict permissions and monitoring.
How much will Carbon cost?
Google announced introductory pricing of $2 input and $10 output per million tokens, with higher later rates. Confirm current terms after access is offered.
Conclusion: a powerful announcement with deliberate safeguards
Gemini 4 Carbon represents a claimed step forward in coding and defensive security, not a blanket security guarantee or an already-open API. Developers should evaluate primary-source claims, watch the phased rollout and prepare controlled tests. For secure software engineering planning, contact RKWS.
Primary source: Google, Introducing Gemini 4 Carbon, 28 October 2026.
Frequently asked questions
Is Gemini 4 Carbon available to everyone?
No. Google's 28 October 2026 announcement limits initial access to a subset of cyber defenders and says more trusted partners will be added through the Fairwind Program before broader release.
How is Gemini 4 Carbon different from Gemini 4 Argon?
Google reports improvements in long-horizon coding, software security and alignment relative to Argon. Carbon has a more restricted initial rollout; those improvements are vendor-published evaluations, not independent guarantees.
What cybersecurity benchmarks did Gemini 4 Carbon achieve?
Google reported 88.2% on SEC-bench Pro, 54.8% on ExploitGym and 71.0% on CWE-bench, in stated benchmark conditions and without its deployment guardrails applied.
What pricing has Google announced for Gemini 4 Carbon?
Google announced introductory prices of $2 per million input tokens and $10 per million output tokens, with a later price of $4 and $20 respectively. These are announced rates for a future wider launch, not evidence of general API availability on 28 October.
Does Gemini 4 Carbon guarantee secure code?
No. The benchmarks and internal studies show progress under specific conditions; they do not certify generated code or replace human review, tests and authorised security assessment.
