Hi!
GeminiLanguageModel currently uses the generateContent / streamGenerateContent endpoints. Google's docs now recommend the Interactions API for all new projects and say all new models, tools and agent features will launch there. generateContent is still supported but is now called legacy.
Would you be open to adding Interactions API support, either as an option on GeminiLanguageModel or as a separate model type? Some benefits:
- Real tool-call IDs, instead of IDs generated on the client
system_instruction as its own field
- Optional server-side conversation history via previous_interaction_id
Docs:
If okay i can work on it and raise PR
Thanks!
Hi!
GeminiLanguageModelcurrently uses thegenerateContent/streamGenerateContentendpoints. Google's docs now recommend the Interactions API for all new projects and say all new models, tools and agent features will launch there.generateContentis still supported but is now called legacy.Would you be open to adding Interactions API support, either as an option on
GeminiLanguageModelor as a separate model type? Some benefits:system_instructionas its own fieldDocs:
If okay i can work on it and raise PR
Thanks!