I'm glad the article questions _whether this is even a problem_, but it seems they tried to answer it and failed to come up with a convincing argument:
> I don't get it. It's a very optional feature that you have to:
> Go out of your way to enable, supply your own API key
> (and pay for it yourself), enable something that is not
> enabled by default. Why are people reacting so strongly
> to this?
... and the article's answer(s), which I don't think are a very convincing rebuttal: > A lot of it boils down to having this "shoved down
> their throats". It's the fact that it's being added
> to a tool without the user having the agency to decide
> if they want it to be added or not.
> I think that one of the greatest errors that was made
> with putting this in iTerm2 was making a big show of it,
> and by not letting you use local models (such as with
> Ollama) instead of having OpenAI be the only option.
I mean, this is open-source. You get a lot of features without any agency here, you are free to edit those out and it has no impact if you don't use it.If someone wants a local model, why not submit a PR instead of complaining? Local models have OpenAI compatibility! https://ollama.com/blog/openai-compatibility
* EDIT: I see that the OpenAI URL is configurable under Advanced > Experimental > URL for AI API. Perhaps this already works?