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
This used to work before the 0.9 update, but now it's broken.
I tried using the stable version model: googleai/gemini-1.5-pro, but it performs poorly (doesn't return JSON according to my schema). The latest version is much better at respecting the schema.
Please bring back the ability to use the latest versions!
To Reproduce
Run the prompt
Error Model googleai/gemini-1.5-pro-latest not found
Expected behavior
Prompt should complete successfully
Screenshots
If applicable, add screenshots to help explain your problem.
Runtime (please complete the following information):
OS: MacOS
Version 0.9
** Node version
run node --version at paste here
node --version
v18.20.5
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Just one point of clarification, the model names have been streamlined a bit; gemini-1.5-pro will always correspond to the current stable version. If you are OK with preview versions, you can still do that as well by providing config.version.
Describe the bug
Set up a .prompt file like this:
This used to work before the 0.9 update, but now it's broken.
I tried using the stable version
model: googleai/gemini-1.5-pro
, but it performs poorly (doesn't return JSON according to my schema). The latest version is much better at respecting the schema.Please bring back the ability to use the latest versions!
To Reproduce
Model googleai/gemini-1.5-pro-latest not found
Expected behavior
Prompt should complete successfully
Screenshots
If applicable, add screenshots to help explain your problem.
Runtime (please complete the following information):
** Node version
node --version
at paste herenode --version
v18.20.5
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: