Alacritty? Kitty? Hyper?
Alacritty? Kitty? Hyper?
This manufactured outrage is absurd. iTerm2 has been the most solid and conservative terminal I’ve ever used and people are pretending they jumped the shark with this feature.
Nobody actually believes OpenAI is giving away billions of dollars in free compute just so we don't have to memorize awk syntax...
To compare it to crypto is just silly. Yes they both are over hyped and use GPUs/power but that’s about where the similarities end. Real people (not just techbros speed-running why we have regulations in finance) get value from LLMs today, not some mythical “one day we will all use bitcoin”-bullshit.
iTerm, since they don't do that. Just keep it disabled.
Unless you consider any terminal that lets you make network calls to OpenAI = OpenAI snooping around.
If your auditor does not believe that with the checkbox unchecked and no API key provided, iTerm will not talk to OpenAI, how do they believe any other software you run does not secretly upload stuff to OpenAI?
What's different between a piece of software claiming to not support OpenAI at all vs. one that claims to support OpenAI if the user provides an API key in light of the possibility that both might be lying (if that's an auditors concern)
With iTerm your auditors at least get to check the source code...
As much as I dislike the current trend of "AI ALL THE THINGS", I don't think supporting it as a completely optional feature is in any way problematic.
There is no checkbox for that, at least I can't find any and I've been looking quite hard.
There is:
- a text input field for the OpenAI API key (by default empty)
- a text input field named "AI Prompt"
- a "Model" dropdown (which doesn't have a "None" option)
- ...and a Token Limit number input field
...that's it. It also doesn't say anywhere that the key field being empty means that the feature is disabled.
A better UI design would have been a checkbox at the top that's disabled by default, and all the detailed UI fields being greyed out and disabled until that checkbox is enabled.
It has been a while since the last release… I don’t mind staying outdated for some more time.
Also, I’m not sure if the openai thingy is mandatory.
The Preferences panel doesn't have a single indicator which says whether the AI integration is activated or not. It's probably just bad UI design and not mischief, but I was instantly put off by what initially looked like a dark pattern.
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.
> It requires you to supply an OpenAI API key.
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?