> It's absolutely rediculous that supporting something, thats opt-in not opt-out is causing a ruckus
iTerm is pretty extensible, and there are other ways of making the AI bloat (IMO) opt-in, without including it in the core software.
The biggest issue for me is that it increases the attack surface on iTerm2 with no tangible benefit (to me), I'd be similarly upset if they added an opt-in "Share on Facebook/StackOverflow" feature. I'd seriously consider switching to a purist fork that doesn't integrate social-media sharing as a core-feature of a terminal app.
> Because you’re already using other software that has LLM integration
Oh really, which software would that be? And which other LLM-enabled software connects production environments or has access to auth credentials/tokens?
I don't want LLMs to parrot back code from other projects without understanding what that code does and what my code does. I don't want it to parrot back irrelevant slop.
And I especially don't want it to parrot:
rm -rf $BUILDDIR/ && ./build-project.sh
and just hallucinate the assumption that $BUILDDIR is already defined.
But GitHub doesn't ship copilot as a separate binary. So the threat vector of “AI has no place in my VCS get it out it increases the surface area” is there. So it’s okay for github to have copilot but not iterm2 to have codesierge? Doesn't add up.
The point here is about compliance. I agree it’d be stupid to pipe the output of an LLM to a terminal’s command line. But people are saying they can’t use iterm2 now because compliance says no AI and having an mdm-secure way to disable the functionality is not enough because _there could be a bug_ or something. Yet they’re checking commits, in presumably the same compliance regime, into other software with AI features.
iTerm is pretty extensible, and there are other ways of making the AI bloat (IMO) opt-in, without including it in the core software.
The biggest issue for me is that it increases the attack surface on iTerm2 with no tangible benefit (to me), I'd be similarly upset if they added an opt-in "Share on Facebook/StackOverflow" feature. I'd seriously consider switching to a purist fork that doesn't integrate social-media sharing as a core-feature of a terminal app.