You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pull request #194 added conservative logic to use the native system instructions only when the model name includes the substring gemini-1.5, since gemini-1.0 doesn't support it:
This doesn't apply to newer Gemini versions like gemini-2.0, gemini-exp and learnlm.
In my own local usage I don't care about using the old 1.0 models and simply changed to always use system_instruction=system_message.
In general, I can't really give a 100% robust solution that would be guaranteed to work on all future versions and variants of Gemini, but it's likely they will allow native system instructions for future models.
Less conservative approach would be to use native system instructions by default, unless it's Gemini 1.0. Something like:
I can't make a pull request unless I know exactly what approach the developer prefers. In any case, I don't think that anybody seriously uses Gemini 1.0 anymore, unless for comparison with older models, maybe.
The text was updated successfully, but these errors were encountered:
Pull request #194 added conservative logic to use the native system instructions only when the model name includes the substring
gemini-1.5
, sincegemini-1.0
doesn't support it:This doesn't apply to newer Gemini versions like
gemini-2.0
,gemini-exp
andlearnlm
.In my own local usage I don't care about using the old
1.0
models and simply changed to always usesystem_instruction=system_message
.In general, I can't really give a 100% robust solution that would be guaranteed to work on all future versions and variants of Gemini, but it's likely they will allow native system instructions for future models.
Less conservative approach would be to use native system instructions by default, unless it's Gemini 1.0. Something like:
I can't make a pull request unless I know exactly what approach the developer prefers. In any case, I don't think that anybody seriously uses Gemini 1.0 anymore, unless for comparison with older models, maybe.
The text was updated successfully, but these errors were encountered: