Gemini 3.8 Flash and Flash Cyber: Google's Coding-First Model Doubles Down on Agentic Diligence

·13 min read·Evergreen Tools Team
Laptop screen with code and AI interface

💡 Tool TipEstimating 3.8 Flash spend or validating agent JSON payloads? Use Evergreen Tools' AI Token Counter for cost forecasting, JSON Formatter to validate API configs, and API Tester to exercise the model endpoint before you wire it into production. AI Token Counter, JSON Formatter, API Tester

In early September 2026 Google shipped Gemini 3.8 Flash and Gemini 3.8 Flash Cyber -- its third Flash release in six weeks. The positioning is blunt: this is Google's best reasoning and coding model yet at the same speed and low cost as 3.7 Flash, accelerated by long-running agentic loops designed to recursively evaluate and refine the model. For developers the core narrative is diligence: on complex tasks 3.8 works harder, executing extra reasoning steps and calling tools iteratively until the answer survives its own critique. That design shows up in the numbers: at Flash pricing it now lands near models that cost several times more per token. It also solves long-horizon engineering problems end to end on DeepSWE v1.1, beating most larger frontier models at a fraction of the cost.

1. A Flash Every Two Weeks

3.8 Flash lands three weeks after 3.7 Flash and six weeks after the previous Flash release. The price band did not move -- 0.75 USD per million input tokens and 3.75 USD per million output tokens -- but performance clearly did, with Google reporting results that often approach higher-cost frontier models. For budget-conscious teams this is the important curve: keep planning at Flash prices, get near-flagship coding and reasoning quality.

// Gemini 3.8 Flash pricing: 0.75 USD per million input tokens,
// 3.75 USD per million output tokens -- the same low band as
// 3.7 Flash, with markedly better coding and reasoning scores.
const PRICING = {
  "gemini-3.8-flash": { inputPerM: 0.75, outputPerM: 3.75 },
  "gemini-3.7-flash": { inputPerM: 0.75, outputPerM: 3.75 },
};

function estimateCost(tokens, model) {
  const p = PRICING[model];
  return (
    (tokens.input / 1_000_000) * p.inputPerM +
    (tokens.output / 1_000_000) * p.outputPerM
  );
}

2. Beyond Benchmarks: It Actually Works Harder

The performance story is a design choice: on complex tasks 3.8 Flash exhibits greater diligence. It executes extra reasoning steps and calls tools iteratively, and at higher effort levels it may spend more tokens to maximize output quality. On DeepSWE v1.1, a long-horizon software engineering benchmark, it autonomously solves complex engineering problems end to end, beating most larger frontier models at a fraction of their cost. It also leads specialist domains such as Vals Finance Agent V2 and Harvey's Legal Agent Benchmark, with a 54.9 percent score on HLE-Verified.

Circuit board representing model infrastructure
{
  "model": "gemini-3.8-flash",
  "effort": "medium",
  "agenticLoop": {
    "enabled": true,
    "recursiveRefine": true,
    "maxIterations": 6,
    "note": "3.8 works harder on complex tasks: extra reasoning
             steps and iterative tool calls until the answer
             survives its own critique pass"
  },
  "tools": [
    { "name": "read_file", "mode": "granted" },
    { "name": "run_tests", "mode": "granted" },
    { "name": "git_commit", "mode": "human_approval" }
  ]
}

3. Efficiency First? 3.7 Flash Stays

Working harder means a complex task can burn more tokens at the same price. Google's answer is the effort dial plus a two-track strategy: when compute efficiency is the hard constraint, use lower effort levels to minimize token overhead, or keep using 3.7 Flash, which remains fully supported. In practice, route by task complexity instead of adopting one model everywhere: simple jobs to 3.7, SWE and finance or legal domain work to 3.8.

// Route by task difficulty, not by habit. 3.8 Flash costs the
// same as 3.7 Flash but spends more tokens when a task is hard;
// for efficiency-first workloads 3.7 Flash remains supported.
function routeTask(task) {
  if (task.complexity === "low" && task.budget === "strict") {
    return "gemini-3.7-flash";
  }
  if (task.kind === "swe" || task.domain === "finance" ||
      task.domain === "legal") {
    return "gemini-3.8-flash";
  }
  return "gemini-3.8-flash";
}

// DeepSWE v1.1: 3.8 Flash solves long-horizon engineering tasks
// end to end, beating most larger frontier models at a fraction
// of the cost. Domain wins: Vals Finance Agent V2, Harvey Legal.

4. Flash Cyber: A Defender-Grade Tier

3.8 Flash Cyber is the most meaningful part of this release for security teams, available to a set of trusted defenders through the Fairwind Program. It demonstrates frontier-level performance in autonomous vulnerability discovery on CyberGym, surpassing both 3.5 Flash Cyber and significantly larger frontier models, and exceeds 70 percent success across an internal benchmark spanning 20 programming languages. On CWE-Bench it posts a 47.2 percent pass@1, within a hair of a leading frontier model's 47.8 percent at far lower cost -- and Google already uses it to secure code across the company.

Cybersecurity defense operations interface

5. Safety Boundary: Fix, Don't Forge

Google stresses that Flash Cyber prioritized vulnerability fixing over offensive capabilities like exploitation from the start. The models ship with safeguards against misuse in CBRN and cyber-offense domains, while the Cyber variant opens a more complete cyber capability set to trusted defenders. For security teams the practical effect is a find-then-fix scanning agent you can point at real codebases while keeping exploit generation off the tool surface.

// The agent loop that 3.8 was trained for: run, critique, refine.
// Recursive self-evaluation is what turns a 54.9 percent
// HLE-Verified score into dependable long-horizon behavior.
function agenticRun(task, maxIterations) {
  let draft = plan(task);
  for (let i = 0; i < maxIterations; i++) {
    const result = execute(draft);
    const critique = evaluate(result, task.acceptance);
    if (critique.pass) return result;
    draft = refine(draft, critique.notes);
  }
  return { status: "needs_review", draft };
}

6. How to Adopt It

Start with a cost-quality replay on your own task set: the same prompts against 3.7 Flash and 3.8 Flash across effort levels, comparing completion rate and token bill. Then route by domain: finance, legal, and cross-repo SWE work to 3.8; simple budget-strict jobs stay on 3.7. Finally, copy 3.8's critique-then-refine loop into your own agent orchestration -- it is not just a model property, it is an architecture pattern worth reusing. A side note for teams already on 3.7 Flash: the upgrade risk is low, because the price band and the API surface are unchanged, and hard tasks simply get a more diligent executor.

// Flash Cyber is defense-first by design: vulnerability finding
// and patching, not exploitation. CWE-Bench pass@1 of 47.2
// percent sits near a leading frontier model's 47.8 percent at
// significantly lower cost.
const defenderPolicy = {
  allowVulnerabilityDiscovery: true,
  allowFixGeneration: true,
  allowExploitDevelopment: false,
  cbrnSafeguards: "enforced",
  access: "fairwind_trusted_defenders_only",
  benchmark: {
    cyberGym: "frontier_level",
    internal20Languages: "above_70_percent",
    cweBenchPassAt1: "47.2_percent",
  },
};

📌 Frequently Asked Questions

Is Gemini 3.8 Flash priced the same as 3.7 Flash?

Yes: 0.75 USD per million input tokens and 3.75 USD per million output tokens. But 3.8 can spend more tokens on complex tasks because it works harder; for efficiency-first workloads use lower effort levels or keep 3.7 Flash.

Is Gemini 3.8 Flash priced the same as 3.7 Flash?

Yes: 0.75 USD per million input tokens and 3.75 USD per million output tokens. But 3.8 can spend more tokens on complex tasks because it works harder; for efficiency-first workloads use lower effort levels or keep 3.7 Flash.

Is Gemini 3.8 Flash priced the same as 3.7 Flash?

Yes: 0.75 USD per million input tokens and 3.75 USD per million output tokens. But 3.8 can spend more tokens on complex tasks because it works harder; for efficiency-first workloads use lower effort levels or keep 3.7 Flash.

Is Gemini 3.8 Flash priced the same as 3.7 Flash?

Yes: 0.75 USD per million input tokens and 3.75 USD per million output tokens. But 3.8 can spend more tokens on complex tasks because it works harder; for efficiency-first workloads use lower effort levels or keep 3.7 Flash.

Is Gemini 3.8 Flash priced the same as 3.7 Flash?

Yes: 0.75 USD per million input tokens and 3.75 USD per million output tokens. But 3.8 can spend more tokens on complex tasks because it works harder; for efficiency-first workloads use lower effort levels or keep 3.7 Flash.

Where does 3.8 Flash actually beat larger models?

Google reports it outperforms most larger frontier models on DeepSWE v1.1 end-to-end software engineering at a fraction of the cost, and leads domain benchmarks like Vals Finance Agent V2 and Harvey's Legal Agent Benchmark, with 54.9 percent on HLE-Verified.

Where does 3.8 Flash actually beat larger models?

Google reports it outperforms most larger frontier models on DeepSWE v1.1 end-to-end software engineering at a fraction of the cost, and leads domain benchmarks like Vals Finance Agent V2 and Harvey's Legal Agent Benchmark, with 54.9 percent on HLE-Verified.

Where does 3.8 Flash actually beat larger models?

Google reports it outperforms most larger frontier models on DeepSWE v1.1 end-to-end software engineering at a fraction of the cost, and leads domain benchmarks like Vals Finance Agent V2 and Harvey's Legal Agent Benchmark, with 54.9 percent on HLE-Verified.

Where does 3.8 Flash actually beat larger models?

Google reports it outperforms most larger frontier models on DeepSWE v1.1 end-to-end software engineering at a fraction of the cost, and leads domain benchmarks like Vals Finance Agent V2 and Harvey's Legal Agent Benchmark, with 54.9 percent on HLE-Verified.

Where does 3.8 Flash actually beat larger models?

Google reports it outperforms most larger frontier models on DeepSWE v1.1 end-to-end software engineering at a fraction of the cost, and leads domain benchmarks like Vals Finance Agent V2 and Harvey's Legal Agent Benchmark, with 54.9 percent on HLE-Verified.

What is different about Flash Cyber?

Flash Cyber is tuned for defender work: vulnerability discovery and patching rather than exploitation. It reaches frontier-level results on CyberGym, exceeds 70 percent success on a 20-language benchmark, and scores 47.2 percent pass@1 on CWE-Bench. It is limited to trusted defenders via the Fairwind Program.

What is different about Flash Cyber?

Flash Cyber is tuned for defender work: vulnerability discovery and patching rather than exploitation. It reaches frontier-level results on CyberGym, exceeds 70 percent success on a 20-language benchmark, and scores 47.2 percent pass@1 on CWE-Bench. It is limited to trusted defenders via the Fairwind Program.

What is different about Flash Cyber?

Flash Cyber is tuned for defender work: vulnerability discovery and patching rather than exploitation. It reaches frontier-level results on CyberGym, exceeds 70 percent success on a 20-language benchmark, and scores 47.2 percent pass@1 on CWE-Bench. It is limited to trusted defenders via the Fairwind Program.

What is different about Flash Cyber?

Flash Cyber is tuned for defender work: vulnerability discovery and patching rather than exploitation. It reaches frontier-level results on CyberGym, exceeds 70 percent success on a 20-language benchmark, and scores 47.2 percent pass@1 on CWE-Bench. It is limited to trusted defenders via the Fairwind Program.

What is different about Flash Cyber?

Flash Cyber is tuned for defender work: vulnerability discovery and patching rather than exploitation. It reaches frontier-level results on CyberGym, exceeds 70 percent success on a 20-language benchmark, and scores 47.2 percent pass@1 on CWE-Bench. It is limited to trusted defenders via the Fairwind Program.

What does working harder mean in practice?

The model executes extra reasoning steps and iterative tool calls on complex tasks until its output survives recursive self-evaluation. Higher effort levels may use more tokens; lower levels minimize overhead.

What does working harder mean in practice?

The model executes extra reasoning steps and iterative tool calls on complex tasks until its output survives recursive self-evaluation. Higher effort levels may use more tokens; lower levels minimize overhead.

What does working harder mean in practice?

The model executes extra reasoning steps and iterative tool calls on complex tasks until its output survives recursive self-evaluation. Higher effort levels may use more tokens; lower levels minimize overhead.

What does working harder mean in practice?

The model executes extra reasoning steps and iterative tool calls on complex tasks until its output survives recursive self-evaluation. Higher effort levels may use more tokens; lower levels minimize overhead.

What does working harder mean in practice?

The model executes extra reasoning steps and iterative tool calls on complex tasks until its output survives recursive self-evaluation. Higher effort levels may use more tokens; lower levels minimize overhead.

How should I integrate 3.8 Flash into production?

Run a cost-quality replay across 3.7 and 3.8 at several effort levels first, then route by task complexity and domain. Enable tool calling with human approval for write actions and validate outputs against schemas.

How should I integrate 3.8 Flash into production?

Run a cost-quality replay across 3.7 and 3.8 at several effort levels first, then route by task complexity and domain. Enable tool calling with human approval for write actions and validate outputs against schemas.

How should I integrate 3.8 Flash into production?

Run a cost-quality replay across 3.7 and 3.8 at several effort levels first, then route by task complexity and domain. Enable tool calling with human approval for write actions and validate outputs against schemas.

How should I integrate 3.8 Flash into production?

Run a cost-quality replay across 3.7 and 3.8 at several effort levels first, then route by task complexity and domain. Enable tool calling with human approval for write actions and validate outputs against schemas.

How should I integrate 3.8 Flash into production?

Run a cost-quality replay across 3.7 and 3.8 at several effort levels first, then route by task complexity and domain. Enable tool calling with human approval for write actions and validate outputs against schemas.