> PS: even the changelog doesn't explicitly state that the feature is disabled by default, only indirectly by stating that one needs an OpenAI key because requests cost money.
The changelog reads
> You will need to provide an OpenAI API key since GPT costs money to use.
One can only misinterpret that to mean the feature is auto-enabled accidentally on purpose. The fact that you cared to edit your comment with that excuse but didn't retract even a single falsehood you spread all over this thread is bad enough. But to continue to pretend that it doesn't require a paid API key even after you explicitly acknowledged that it does? Outright malicious.
> AFAIK using OpenAI through the webpage doesn't cost money, why should I assume that using it through the REST API is any different?
The changelog reads
> You will need to provide an OpenAI API key since GPT costs money to use.
One can only misinterpret that to mean the feature is auto-enabled accidentally on purpose. The fact that you cared to edit your comment with that excuse but didn't retract even a single falsehood you spread all over this thread is bad enough. But to continue to pretend that it doesn't require a paid API key even after you explicitly acknowledged that it does? Outright malicious.
> AFAIK using OpenAI through the webpage doesn't cost money, why should I assume that using it through the REST API is any different?
https://news.ycombinator.com/item?id=40426922