-
Notifications
You must be signed in to change notification settings - Fork 297
TUI - Prompted for entering openAI API keys when executing gptscript that is chat enabled using a local provider. #510
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
Comments
Similar issue is also seen when testing with "--ui" option with local provider. User is prompted to enter openai api keys and chat completion requests are sent to openai instead of being sent to local provider. |
This issue is seen when testing with any provider other than the default gpt provider.
|
@sangee2004 just merged a fix (#541) to main. Please verify the issue is resolved when you get the chance. |
@njhale When i try to TUI with other providers , I am not prompted to enter openai api keys anymore. But tool calls do not succeed. In case of local model , i just see a message about
|
The latter issue w/ the anthropic provider should be fixed by #551 |
Tested with gptscript version Able to chat with local provider and Anthropic provider using TUI ( and --disable-tui) option. |
Closing this issue with findings from #510 (comment). We are still not able to launch ui with other providers which is tracked in |
gptscript version v0.8.2+1b5e068f
Steps to reproduce the problem:
On entering an invalid(or empty) openAI API key , the script fails to execute.
Expected Behavior:
User should not be prompted to enter openAI API keys when executing chat scripts with local providers.
Note - When TUI is disabled -
gptscript --disable-cache --default-model 'Llama-3-8b-function-calling-alpha-v1.gguf from http://localhost:1234/v1' --disable-tui examples/bobchat.gpt
, there is no prompting for openai API key and chat completion requests get directed to local models and succeeds.The text was updated successfully, but these errors were encountered: