4 ms·
This was fixed now. The article’s main point still stands IMO. I.e. that iterm2 focused on openai and not some local workflow by default. Optional or not, I’d
by thih9 2y ago
This was fixed now. The article’s main point still stands IMO. I.e. that iterm2 focused on openai and not some local workflow by default.
Optional or not, I’d like core features to be privacy friendly and provider agnostic. Otherwise a plugin might be a better fit.
> 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.
- ephimetheus 2y agoI think you can hardly call it “focused on”, when it’s one feature out many many updates made to the software. Alao I believe you can retarget the calls to a local instance of a model behind an OpenAI compatible API, and it will happily use that. Seems like lots of knee jerking going on.
- thih9 2y agoI meant “focused on” in the sense that AI features specifically are focused on openai, to the point of mentioning openai only in the changelogs. I haven’t seen an official demo of using ai features with a local instance. I believe it should be the other way round, the focus should be on local (because again, this is provider agnostic and privacy friendly).
- joshstrange 2y agoYou can change the endpoint, which anyone could learn from reading the comments on the release yesterday or reading the wiki > 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. There is not a single line this is that is true. A big show was not made and you can use Ollama with it. The “big show” was made by other people not the developer behind iTerm2.