-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gemini 2.0 API Key Configuration Unclear #479
Comments
Hi there, you can set GEMINI_API_KEY in backend/.env and then, in generate_code.py set variant_models = [Llm.GPT_4O_2024_11_20, Llm.GEMINI_2_0_FLASH_EXP] or whatever LLM combo you want to have. Make sure to set this right before this line: Let me know if this works. |
replaced with and now it works variant_models = []
|
except generating from video. I dont know why but Flash 2.0 supports video inputs |
Yup, video support is very alpha and currently only works with Claude Opus. It hasn't been updated in a while. |
When I use the GEMINI model, I encounter the error in the picture when it requests reordering. I would like your support regarding this issue. Excellent work. Thanks. ERROR:
Screencast.from.2025-02-08.17-55-17.webm |
Looks like follow-up prompts are failing but first prompts are working? Ah, I think currently the repo only supports Gemini for the initial generation. The code needs to be modified to do a better translation of the messages from the OpenAI format to the Gemini format for follow-ups to work. So yeah, the Gemini implementation is a little hacky at the moment. |
@abi Thanks |
Unable to determine the correct location and variable name for inserting the Gemini 2.0 API key in the project configuration.
To Reproduce
Attempt to integrate Gemini 2.0 API
Search through configuration files
Unable to identify correct key insertion point
Experiencing configuration uncertainty
Additional Details
Specific questions:
Where should the Gemini 2.0 API key be placed?
What is the exact variable name for the API key?
The text was updated successfully, but these errors were encountered: