- Issue created by @erindarri
- π¬π§United Kingdom scott_euser
This issue would be redundant if we get β¨ Use the AI module under the hood Active in.
- π¬π§United Kingdom scott_euser
OpenAI is moving toward using project API keys in lieu of personal API keys. The project API keys are 132 characters, so they get truncated and cause an incorrect key error. Personal API keys are only 95 characters and fit in the short text field.
(This is a bit fuzzy for me... I 'm not sure what the best approach would be)
Change the field type to long text field to accommodate a longer API key, or maybe add a second field for a project API key to be used instead.
Alternatively, update documentation that a personal API key needs to be used and not a project API key.
Probably just update documentation.
Probably none, if documentation is just updated or if the field can be updated to hold more than 128 characters. Otherwise, possibly adding a field so there are two options for API keys? That seems cumbersome.
Would need to update API checking to check for either API key length.
I don't know.
Active
1.0
Documentation
This issue would be redundant if we get β¨ Use the AI module under the hood Active in.