Skip to content

fix(gemini): update default Gemini model to gemini-3.8-flash - #52

Merged
getdownandcode merged 2 commits into
mainfrom
fix/update-to-gemini-3-8-flash
Oct 1, 2026
Merged

getdownandcode merged 2 commits into
mainfrom
fix/update-to-gemini-3-8-flash

Conversation

@getdownandcode

Copy link
Copy Markdown
Owner

Summary

  • Upstream Google Gemini API recommends gemini-3.8-flash as the current active flash model with fresh quota capacity.
  • Updates default model across Settings, GeminiClient, LLM factory, docker-compose, and .env.example.
  • Exposes RUN_TIMEOUT_S in docker-compose.yml with default 60s.
  • Updates unit tests in test_config, test_gemini_adapter, and test_llm_factory.

Verification

  • ruff check . -> Passed
  • ruff format --check . -> Passed
  • mypy agentkit tests -> Passed
  • pytest -q -> Passed (100%)

- Update unit tests in test_config, test_gemini_adapter, and test_llm_factory to assert gemini-3.8-flash
- Set default LLM_MODEL to gemini-3.8-flash across settings, adapter, factory, docker compose, and .env.example
- Expose RUN_TIMEOUT_S in docker-compose.yml

@getdownandcode getdownandcode left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strict Peer Review:

  1. Model standard: Standardizes on gemini-3.8-flash, the model recommended by Google Gemini API with verified live quota and active tool calling.
  2. Settings: Exposes configurable RUN_TIMEOUT_S in docker compose while preserving standard 60s default.
  3. Tests: All config, factory, and adapter tests updated and passing.

Approved for rebase-merge.

@getdownandcode
getdownandcode merged commit 0cf2eeb into main Oct 1, 2026
1 check passed
@getdownandcode
getdownandcode deleted the fix/update-to-gemini-3-8-flash branch October 1, 2026 15:30
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.

1 participant