Skip to content

Add native Google provider config and doctor support#159

Open
lazyeo wants to merge 5 commits intoNarcooo:masterfrom
lazyeo:feat/google-provider
Open

Add native Google provider config and doctor support#159
lazyeo wants to merge 5 commits intoNarcooo:masterfrom
lazyeo:feat/google-provider

Conversation

@lazyeo
Copy link
Copy Markdown

@lazyeo lazyeo commented Apr 6, 2026

Summary

  • adds the native Google/Gemini provider path in the core provider layer
  • wires provider: google through project config, global config, init scaffolding, and doctor/config help text
  • supports Gemini-native tool/function calling turns, including replaying tool results and preserving thoughtSignature across the loop
  • updates README docs (zh/en/ja) to show native Google usage and the current recommended default model

What was validated online

Validated against the live Google native API:

  • non-stream text generation via generateContent
  • Gemini-native function/tool calling
  • replaying tool results back into Gemini-native turns
  • preserving and forwarding thoughtSignature in tool-call replay
  • Gemini 2.5 models as the current recommended path, plus 3.x preview models as validated preview options

Current recommendation

  • default stable recommendation: gemini-2.5-flash
  • gemini-3.x preview models were validated, but are not presented as the default stable recommendation in docs/help/config scaffolding

Current boundaries

This PR documents and ships the validated Google-native scope above. It does not claim blanket provider parity beyond what was exercised.

Known boundary notes:

  • the validated path is focused on native generation + native tool-calling loops
  • preview Gemini 3.x models remain preview choices
  • any broader parity claims should wait for additional targeted validation

@lazyeo
Copy link
Copy Markdown
Author

lazyeo commented Apr 8, 2026

Quick update: this branch has been rebased onto the latest upstream master (currently aligned with the v1.1.1 line), and the Google provider commits were replayed cleanly.

Post-rebase, the Google-provider-related core tests still pass locally, and the branch remains focused on:

  • native Google provider config + doctor support
  • native Gemini tool calling
  • thoughtSignature preservation during tool replay
  • docs/help/init guidance for the Google native path

@lazyeo lazyeo force-pushed the feat/google-provider branch from 2d2e73e to b71feae Compare April 9, 2026 06:57
@lazyeo lazyeo force-pushed the feat/google-provider branch from b71feae to 867acca Compare April 9, 2026 07:01
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