Skip to content

chore: default Gemini Flash model to gemini-3.8-flash - #5364

Merged
nicoloboschi merged 1 commit into
mainfrom
chore/gemini-3.8-flash-defaults
Oct 7, 2026
Merged

nicoloboschi merged 1 commit into
mainfrom
chore/gemini-3.8-flash-defaults

Conversation

@cdbartholomew

Copy link
Copy Markdown
Contributor

Why

Google is retiring Gemini 3.6 Flash (2026-11-19) and 3.7 Flash (2027-01-28). After those dates, requests to them return 404. Anyone relying on these defaults would start failing.

Gemini 3.8 Flash is the generally available successor, at the same per-token price.

Change

  • Hermes integration: the default model for the gemini provider goes from gemini-3.6-flash to gemini-3.8-flash.
  • System evals: the default HINDSIGHT_EVAL_LLM_MODEL in replay_delta_ops.py and the README example go from gemini-3.7-flash to gemini-3.8-flash.
  • Pricing table: the 3.6 and 3.7 entries in refresh_cost.py are kept, so cost reports on historical runs still work.

Testing

  • The Hermes integration test suite passes (112 tests).
  • replay_delta_ops.py compiles.
  • A live check confirmed gemini-3.8-flash answers generateContent and makes the same tool call as 3.6 Flash on a function-calling probe. It has the same 1M input / 65K output limits.

Google is retiring Gemini 3.6 Flash (2026-11-19) and 3.7 Flash
(2027-01-28); after those dates requests to them return 404. 3.8 Flash is
the generally available successor at the same price.

- hermes integration: default model for the gemini provider
- system evals: default HINDSIGHT_EVAL_LLM_MODEL in replay_delta_ops and
  the README example

Pricing entries for 3.6/3.7 stay in refresh_cost.py so historical runs
still cost out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants