-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Description
First of all, love the whole project!
I have been using A0 with the Openrouter provider successfully, then tried using a custom provider (operated by my workplace). I ran into the issues detailed below.
-
The OPENAI_API_BASE and OPENAI_API_KEY variables cannot be read successfully from the Secrets management/Variables section: not in the global and not in the project-level settings, either. (However, in the global settings, I can successfully input these into the dedicated input fields under Chat model/Utility model, etc., so I think the problem might be similar as below for the project-level setting.)
-
In the project-level settings, A0 seems to store the inputted environment variables in the file PROJECT_NAME/.a0proj/variables.env, but when actually parsing the environment, it is looking for the file PROJECT_NAME/.env, which does not get created, even after restarting A0.
-
If I set the model provider back to Openrouter, but the API base URL is still set in the GUI panel under Chat model/Utility model/etc. (to the custom one that I used earlier), LiteLLM will display an error that the session has expired or the token is invalid (it probably still queries the custom API base URL instead of the Openrouter default, even when the provider is set back to Openrouter). Maybe this is by design though as even mainstream providers can operate alternative URL endpoints…?