-
Notifications
You must be signed in to change notification settings - Fork 99
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
Noodl AI (GPT-3) not working/ asks for GPT 4 API key #25
Comments
I am having the same issue. |
Same. |
The AI builder does not seem to work for the Open Source version. It only works for the legacy 2.9 commercial version. |
There is an issue with GPT 4 the open source version which requires a build from source to work. Perhaps try that to see if the basic GPT works from that version. |
I've already tried building from source, same problem. |
I assume that the Noodle team is looking into refactoring Noodle AI? While gpt-3 is selectable, the code doesn't seem to handle the gpt-3 model properly. Distinction between limited-beta and full-beta is described, but not handled as mentioned. Is it worth refactoring this now? or are there bigger plans for the Clippy? I did a first refactoring making 3.5-turbo active as LimitedBeta. Only /Function is available. With every ChatGPT request resulting in Fatal Error. I guess it needs a propper refactoring. |
Same issue here... any idea ? |
@davidflips17 this issue is solved in the code, but there is no new release by the remaining Noodl team. I suggest running the editor from source, or using one of the forks https://github.com/fluxscape/fluxscape or https://github.com/The-Low-Code-Foundation/Code-Crusher. |
Thanks for your response, @erictuvesson. Ended up downloading fluxscape |
Did this end up working for you? I've tried both but keep running into the same error. |
When activating Open AI gpt 3 option in the settings and then trying to use the AI function in the editor it asks you to enter an API key for GPT 4 even though gpt 3 is the one selected in the settings.
The text was updated successfully, but these errors were encountered: