# Atlas with Gemini 2.5 Flash: The Workhorse small_model Pick for 2026 > Gemini 2.5 Flash reads a 1,048,576 token context at $0.3 per Mtok, a sixth of frontier tier input pricing. Gemini 2.5 Flash is the workhorse fast model of the 2.5 generation and the model most Atlas users should point their small_model slot at. It is reasoning capable, carries the full 1,048,576 token context and a 65,536 token output ceiling, and costs $0.3 per Mtok input and $2.5 per Mtok output. That input price is a sixth of what a frontier tier model charges to read the same repository, which is why gemini-2.5-flash is the right home for the titles, summaries, and subagent calls Atlas makes constantly in the background. ## Key takeaways - Gemini 2.5 Flash costs $0.3 per Mtok input and $2.5 per Mtok output, a sixth of frontier tier input pricing for the same 1,048,576 token window. - Reasoning is enabled with a 65,536 token output ceiling, eight times the 8,192 cap on the 2.0 Flash line. - gemini-2.5-flash is a stable GA id, well suited to Atlas's small_model slot where titles, summaries, and subagents run constantly. - Gemini 2.5 Flash is less reliable than Gemini 2.5 Pro on multi file architectural changes that need sustained reasoning. - Gemini 3 Flash supersedes it with the same window and a stronger checkpoint. ## What is Gemini 2.5 Flash best at inside Atlas? Gemini 2.5 Flash is best at high-frequency background work inside Atlas. At $0.3 per Mtok input against a 1,048,576 token window, gemini-2.5-flash makes a full-repo read cost a fraction of a frontier model, which is exactly the profile Atlas's small_model slot needs. Atlas runs far more model calls than a chat interface does. Atlas fans out work to subagents that can run in the foreground or in parallel background sessions, and each of those subagents needs a model. Atlas also generates session titles and summaries continuously. Routing all of that through gemini-2.5-flash at $0.3 per Mtok input keeps the bill flat while the agent works. Because Atlas searches code with hybrid semantic and keyword retrieval fused by reciprocal rank fusion, the context handed to each background call is already dense and relevant, so Gemini 2.5 Flash rarely needs the full 1,048,576 tokens to be useful. ## Does Gemini 2.5 Flash support reasoning and long outputs? Gemini 2.5 Flash is reasoning enabled and still allowed 65,536 output tokens, unlike the 2.0 Flash line which caps at 8,192. That eight-fold difference in output ceiling is the single biggest reason to prefer gemini-2.5-flash over gemini-2.0-flash for anything that writes code. An output cap is a hard ceiling on how much of a change a model can emit in one turn. Atlas computes a unified diff for every file edit and surfaces it for approval before writing, and a large multi-file diff is a lot of tokens. With 65,536 tokens of headroom, Gemini 2.5 Flash can produce a substantial diff in a single response instead of dribbling it out over several turns. Reasoning being enabled means Gemini 2.5 Flash can also work through a debugging chain rather than pattern-matching at it, which is unusual at the $0.3 per Mtok input tier. ## How do you set Gemini 2.5 Flash as the small_model in atlas.json? Set "small_model": "google/gemini-2.5-flash" in atlas.json to cheapen every background call Atlas makes. The small_model slot drives titles, summaries, and subagents, and at $0.3 per Mtok input against $2.5 per Mtok output, gemini-2.5-flash keeps that constant traffic inexpensive. The split is the point. Leave "model" on a Pro tier checkpoint for the main build loop, where reasoning depth decides whether the diff is correct, and let Gemini 2.5 Flash handle everything else. Confirm the id first with `atlas models google` so you know gemini-2.5-flash resolved, then edit atlas.json. Because gemini-2.5-flash is a stable GA id, the small_model slot will not change behavior under you between sessions. If your work is cost sensitive enough, you can also set Gemini 2.5 Flash as "model" and run the whole agent loop on it. ## What are the tradeoffs of running Atlas on Gemini 2.5 Flash? Gemini 2.5 Flash is less reliable than Gemini 2.5 Pro on multi file architectural changes that need sustained reasoning. Gemini 2.5 Flash is also superseded by Gemini 3 Flash, which offers the same 1,048,576 token window with a stronger checkpoint, so the 2.5 Flash choice is a price and stability choice. Honesty about the ceiling matters here. A refactor that touches many files and requires holding several invariants at once is where Gemini 2.5 Flash starts producing diffs you reject. Atlas's permission system limits the damage: every Atlas tool call is permission-gated against allow, ask, and deny rules before it runs, and Atlas drafts a plan in a read-only plan agent and asks before switching to a build agent. Even so, a rejected diff still costs you a turn. The right pattern is to keep Gemini 2.5 Flash where volume is high and stakes are low, and reach for a Pro tier model when the change is architectural. ## When should you pick a different model than Gemini 2.5 Flash? Pick a different model than Gemini 2.5 Flash when the task demands sustained reasoning across many files, or when you want the newest fast checkpoint. Gemini 3 Flash offers the same 1,048,576 token window with a stronger checkpoint, and Gemini 2.5 Pro is the safer builder for architectural work. Atlas lets you switch the active model and provider on the fly with favorites and recents, so the model choice is per task, not per project. Use /models in the TUI to flip between gemini-2.5-flash and a Pro tier model as the work changes shape. On a bug that spans a call chain, move up. On a batch of mechanical renames or a fan-out of parallel searches, Gemini 2.5 Flash at $0.3 per Mtok input is plenty. If you want to go cheaper still for pure triage, the Flash-Lite tier drops the input price further, at the cost of code generation quality. ## Setup 1. Export GEMINI_API_KEY, or run `atlas login` and choose Google. 2. Run `atlas models google` to confirm gemini-2.5-flash resolved. 3. Set "small_model": "google/gemini-2.5-flash" in atlas.json to cheapen every background call Atlas makes. 4. Optionally set it as "model" too for cost-sensitive agent loops. 5. Use /models in the TUI to flip between it and a Pro tier model per task. ## FAQ ### how much does gemini 2.5 flash cost per million tokens Gemini 2.5 Flash costs $0.3 per Mtok input and $2.5 per Mtok output. The input price is roughly a sixth of what a frontier tier model charges to read the same repository. ### what is the output token limit of gemini 2.5 flash Gemini 2.5 Flash allows 65,536 output tokens, eight times the 8,192 token cap on the Gemini 2.0 Flash line. That headroom is what lets it emit a large unified diff in a single Atlas turn. ### should i use gemini 2.5 flash as the small model in atlas Yes, for most setups. Set "small_model": "google/gemini-2.5-flash" in atlas.json so titles, summaries, and subagent calls run at $0.3 per Mtok input while your main "model" stays on a stronger checkpoint. ### is gemini 2.5 flash good enough for writing code Gemini 2.5 Flash is reasoning capable and handles routine code changes well, but it is less reliable than Gemini 2.5 Pro on multi file architectural changes that need sustained reasoning. ### gemini 2.5 flash vs gemini 2.5 pro in atlas Gemini 2.5 Flash costs $0.3 per Mtok input against Gemini 2.5 Pro's $1.25, and both carry a 1,048,576 token context. Gemini 2.5 Pro is the more reliable builder on architectural work, so use /models to flip per task. ### how do i set up gemini 2.5 flash in atlas Export GEMINI_API_KEY or run `atlas login` and choose Google, then run `atlas models google` to confirm gemini-2.5-flash resolved before setting it in atlas.json. ### has gemini 2.5 flash been replaced Gemini 2.5 Flash is superseded by Gemini 3 Flash, which offers the same 1,048,576 token window with a stronger checkpoint. Gemini 2.5 Flash remains a stable GA id, which some teams prefer for reproducibility. --- Canonical HTML: https://runatlas.sh/resources/models/gemini-2-5-flash Source of truth: aeo_pages row `/resources/models/gemini-2-5-flash` (segment: Models) (this file is generated from it, never hand-edited). Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.