Can Gemini 3.5 Flash Run Locally on Mac? Ollama, MLX & Pricing

October 11, 2026 correction: Google deprecated Gemini 3.5 Flash. Its October 9 model-card update confirms gemini-3.5-flash requests are automatically routed to gemini-3.6-flash. Use gemini-3.6-flash or gemini-3.8-flash directly for new applications. This is cloud inference, not a local Mac checkpoint. Official model status · current API rates.

The older $1.50 input / $9.00 output per million tokens describes historical 3.5 list pricing, not the current billing basis for the routed alias. The historical release and today’s migration are separated below; see the local-vs-cloud Mac guide for runtime details.

What Google announced at I/O 2026

Google I/O 2026 took place on May 19, 2026. Google framed the event as a move into a more agentic Gemini era: models that do not just answer prompts, but can use tools, execute code, handle longer tasks and coordinate agents.¹²³

The central model story was Gemini 3.5. Gemini 3.5 Flash was the first stable model in that family, but its API model ID is now deprecated. Google positions it for agentic coding, long-horizon tasks, tool use and real-world workflows.⁴¹³

Gemini 3.5 Flash outperforms Gemini 3.1 Pro on several coding and agentic benchmarks, including Terminal-Bench 2.1 at 76.2%, GDPval-AA at 1656 Elo, MCP Atlas at 83.6%, and CharXiv Reasoning at 84.2%. Google also says output tokens per second are 4x faster than other frontier models, citing Artificial Analysis. These are vendor-reported figures, not independent Mac measurements.¹³

What Gemini 3.5 Flash is

Gemini 3.5 Flash was Google’s cloud API model; the deprecated model ID now routes to 3.6 Flash. It accepts text, image, video, audio and PDF inputs, and outputs text.⁵⁴

It is useful when you need a cloud model with a large context window, multimodal input, tool calling, code execution, File Search, Search/Maps grounding or Managed Agents.

It is not documented as a local Mac model. The official pages describe API/cloud access and do not document an Apple-Silicon runtime path.⁵⁴

Model ID and specs

The official Gemini API model ID is gemini-3.5-flash.⁵⁴ If a third-party router shows something like google/gemini-3.5-flash, treat that as provider-specific naming.

Gemini 3.5 Flash: no documented local Mac path

For Mac users, this distinction matters more than the benchmark headline. The Google sources reviewed here describe the API/cloud model but no official Ollama, MLX or GGUF path.⁵⁴ That is a source boundary, not proof that no local experiment could ever work.

Apple Silicon accelerates local inference for local runtimes. For Gemini API usage, the important Mac factors are internet reliability, API key handling, cost controls, data-flow decisions and developer tooling.⁵

API setup on Mac

Use Google AI Studio to create a Gemini API key. Store it as GEMINI_API_KEY.⁵⁴

export GEMINI_API_KEY="your-api-key-here"

Do not expose API keys in browser code, public GitHub repositories or static Astro pages. Use a backend, serverless function, edge function or secure secret management. For local development, load the key from an environment variable or a local secret store and never commit it.

Python

from google import genai

client = genai.Client()

response = client.models.generate_content(
    model="gemini-3.6-flash",
    contents="Explain unified memory on Apple Silicon in three sentences.",
)

print(response.text)

Python with thinking level

from google import genai
from google.genai import types

client = genai.Client()

response = client.models.generate_content(
    model="gemini-3.6-flash",
    contents="Analyze the trade-offs between local AI and cloud AI on Mac.",
    config=types.GenerateContentConfig(
        thinking_config=types.ThinkingConfig(thinking_level="high")
    ),
)

print(response.text)

JavaScript

import { GoogleGenAI } from "@google/genai";

const ai = new GoogleGenAI({});

async function main() {
  const response = await ai.models.generateContent({
    model: "gemini-3.6-flash",
    contents: "Create a checklist for a hybrid local/cloud AI workflow on Mac."
  });

  console.log(response.text);
}

main();

REST

curl "https://generativelanguage.googleapis.com/v1beta/models/gemini-3.6-flash:generateContent" \
  -H "x-goog-api-key: $GEMINI_API_KEY" \
  -H "Content-Type: application/json" \
  -X POST \
  -d '{
    "contents": [{
      "parts": [{
        "text": "Summarize the differences between local AI on Mac and Gemini 3.5 Flash."
      }]
    }]
  }'

GenerateContent or Interactions API?

The examples above use generateContent because it is the simplest way to show a first working request. Interactions is generally available, but Google’s current matrix reserves Batch, explicit caching, custom safety settings and automatic Python function calling for generateContent. Select the API based on supported features.⁴⁶

The older Gemini 3 developer guide is now marked deprecated. For Gemini 3.5 Flash, use the current “What’s new” and model pages as the primary references.⁷⁴

Use this split:

• Use generateContent for simple prompts, existing integrations, quick tests and cases where you need features that are not yet available in Interactions API, such as Batch API or explicit caching.
• Use the Interactions API for new agentic apps, server-side history management, observable execution steps, tool orchestration, background tasks and future Gemini capabilities.

Important privacy/cost detail: Interactions API stores interaction objects by default (store=true) for server-side state, background execution and observability. For Paid Tier projects, the current documentation lists configurable retention windows of 7, 14, 28 or 55 days. You can opt out with store=false, but that disables stored-state workflows such as previous_interaction_id and is incompatible with background execution.⁶

Thinking levels and thought preservation

Gemini 3.5 Flash supports thinking. For Gemini 3.5 Flash, use thinking_level, not the older thinkingBudget pattern used by some Gemini 2.5 examples. The current migration lists medium as the default.⁴⁸

Recommended levels:

Thought preservation is handled through thought signatures and conversation history. The GenAI SDK manages this automatically in normal usage. Preserved thoughts can increase input token usage across turns because signatures are sent back with the conversation. Do not promise raw chain-of-thought access. If the API or SDK exposes thought summaries, treat them as controlled summaries, not the full internal reasoning trace.

Pricing: Standard, Batch, Flex, Priority and grounding

Pricing on October 11, 2026: The old 3.5 model ID routes to 3.6 Flash. The following values are 3.6 paid-tier rates through December 31, 2026, USD per million tokens — not active independent 3.5 prices.

3.6 Flash	Input	Output incl. thinking	Cached input
Standard	$0.75	$3.75	$0.075
Batch	$0.375	$1.875	$0.0375
Flex	$0.375	$1.875	$0.0375
Priority	$1.35	$6.75	$0.135

Example: 1M input + 200,000 output currently cost $1.50 at Standard rates. 3.8 Flash has the same 2026 Standard list prices, so claiming it is cheaper than inference already routed from 3.5 would be misleading. Google lists $1.50/$7.50 for both starting January 1, 2027. Earlier 3.5 pricing of $1.50/$9.00 is historical, not current. Tools, grounding and caching storage can cost extra. Google API prices.

1M context: useful, but not free

Gemini 3.5 Flash supports 1,048,576 input tokens and 65,536 output tokens. That is useful for large PDFs, long codebases, multi-file analysis and agent traces. It also increases cost, latency and the chance that irrelevant material distracts the model.

Good long-context habits:

• Structure input with headings and file boundaries.
• Remove irrelevant sections before sending.
• Use File Search or RAG instead of pasting everything into every request.
• Check context caching for repeated large inputs.
• Summarize long conversations.
• Specify output formats strictly.
• Do not blindly copy entire repositories or PDFs into every request.

Managed Agents in the Gemini API

Managed Agents are cloud-based Gemini API agents. A single API call can start an agent that can reason, use tools and execute code in an isolated, ephemeral Linux environment.

Google now uses Gemini 3.8 Flash by default for the managed Antigravity agent and its SDK. The older 3.5 attribution refers to the launch period; this remains cloud execution, not local Mac inference.⁹³

Google’s launch announcement described Managed Agents as rolling out in preview. Treat this as a Google cloud feature whose availability may depend on account, region, API access and product changes.⁹

Antigravity 2.0 and Mac developer workflows

Antigravity 2.0 is Google’s agent-first developer platform and desktop app. It is designed around orchestration: multiple agents, subagents, scheduled tasks and integrations.

For Mac developers, Antigravity is a cloud-agent development environment. It is not local inference: your Mac is the development machine, while Gemini 3.5 Flash and the managed agents run in Google’s cloud ecosystem.

Gemini Spark and the macOS app

Google announced updates to the Gemini app for macOS on May 19, 2026. Gemini Spark was planned for the Gemini desktop app and positioned as an agent that can help with local files and desktop workflows; that is a time-bound product announcement, not a guarantee for every region or account.¹⁰

The key distinction: Gemini Spark is cloud-based. It may interact with desktop context, but it is not a local LLM running on Apple Silicon. Even if Spark can work with local files through the macOS app, the model inference is not local Apple Silicon inference.¹⁰

Use this split:

• Local inference: Ollama, LM Studio, MLX.
• Cloud agents: Gemini Spark, Antigravity, Managed Agents.

Gemini 3.5 Flash vs local AI on Mac

Useful internal next reads: Apple Intelligence vs local AI, Ollama setup, LM Studio vs Ollama, Unified Memory, Best open-weight LLMs and Gemma 4 vs. Qwen3 on Mac.

Privacy, logs and abuse monitoring

Gemini 3.5 Flash is a cloud model. Data leaves your device.

The privacy picture depends on tier, API surface and project configuration:

• Free Tier: according to Google’s pricing page, content may be used to improve Google products.¹¹
• Paid Tier: according to the pricing page, content is not used to improve Google products.¹¹
• Billing-enabled logs: Google’s data logging policy says prompts and responses in logs are not used for product improvement by default, unless you actively share datasets or feedback.¹²
• Abuse monitoring: Google says prompts, contextual information and outputs may be retained for 55 days for misuse detection and policy enforcement.¹³
• Interactions API storage: interactions are stored by default for server-side state and observability; Paid Tier projects can configure 7-, 14-, 28- or 55-day retention windows, with store=false available for stateless requests where compatible.⁶

Do not reduce this to “Google trains on everything” or “paid is automatically fully private.” For sensitive files, use local models, an enterprise/Vertex AI setup, or a formal compliance review.⁶¹²¹³

When Gemini 3.5 Flash makes sense

Use Gemini 3.5 Flash when you need:

• 1M context for long documents or codebases.
• Multimodal input.
• Code execution.
• Function calling and structured outputs.
• File Search.
• Search or Maps grounding.
• Managed Agents or Antigravity workflows.
• Long-horizon cloud tasks.

When local AI is better

Use local AI when you need:

• Private documents to stay on the Mac.
• Offline work.
• Open-weight model experiments.
• Reproducible local benchmarks.
• No per-token API bill.
• Tight control over model files, quantization and runtime.

Start with Ollama or LM Studio if the goal is local inference on Apple Silicon.

Common Gemini 3.5 Flash mistakes

• Confusing the official model ID with provider aliases: in the Gemini API, use gemini-3.5-flash, not necessarily google/gemini-3.5-flash.
• Copying old or unrelated API examples: use the official Google GenAI SDK or REST syntax for Gemini.
• Using outdated thinking parameters: for Gemini 3.x, use the current thinking_level recommendation instead of older budget-style examples from other model generations.⁴⁸
• Looking for Gemini 3.5 Flash in Ollama, LM Studio or MLX: Google does not document an Apple-Silicon local path.⁵⁴
• Filling the 1M context window blindly: long context increases cost, latency and failure surface.
• Mixing Free Tier and Paid Tier privacy assumptions: data use and product-improvement rules differ by tier.¹¹¹²
• Treating Search Grounding as free by default: grounding can create billable search queries after the free allowance.¹¹
• Treating Gemini Spark as local inference: Spark may integrate with Mac workflows, but it is not local Apple Silicon inference.¹⁰
• Treating Computer Use as universally available: Google lists Computer Use as a Preview capability, while image generation and audio generation remain unsupported on this model page. Check the exact API surface and region before relying on it.⁵

Conclusion: Cloud tool with 1M context, no local path

For Mac users, Gemini 3.5 Flash is relevant because it combines 1M context, multimodal input, thinking, tool use, code execution, file search, grounding and Managed Agents in a cloud model.⁵⁴⁹

For private files, offline work and open-weight experimentation, Ollama, LM Studio and MLX remain the better choice. For large context, agentic coding workflows, tool chains and cloud agents, Gemini 3.5 Flash is a practical cloud complement.

The useful question is which data must stay on the Mac and which tasks benefit from Google’s cloud tools. Local models cover many routine tasks; Gemini is relevant when its large context, multimodal inputs or managed tools justify sending data to a cloud service.¹¹¹²¹³

Sources

Footnotes

1. https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-5 ↩ ↩² ↩³

2. https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-collection ↩

3. https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-developer-highlights ↩ ↩² ↩³ ↩⁴

4. https://ai.google.dev/gemini-api/docs/whats-new-gemini-3.5 ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹ ↩¹²

5. https://ai.google.dev/gemini-api/docs/models/gemini-3.5-flash ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹

6. https://ai.google.dev/gemini-api/docs/interactions ↩ ↩² ↩³ ↩⁴

7. https://ai.google.dev/gemini-api/docs/gemini-3 ↩

8. https://ai.google.dev/gemini-api/docs/thinking ↩ ↩²

9. https://blog.google/innovation-and-ai/technology/developers-tools/managed-agents-gemini-api ↩ ↩² ↩³

10. https://blog.google/innovation-and-ai/products/gemini-app/next-evolution-gemini-app ↩ ↩² ↩³

11. https://ai.google.dev/gemini-api/docs/pricing ↩ ↩² ↩³ ↩⁴ ↩⁵

12. https://ai.google.dev/gemini-api/docs/logs-policy ↩ ↩² ↩³ ↩⁴

13. https://ai.google.dev/gemini-api/docs/usage-policies ↩ ↩² ↩³