[asdajksah2123]

Entirely optional features that have a history of not becoming optional anymore in many other applications and quite evidently can easily be installed as a plugin instead.

Further, why in the world would you include a completely optional feature that runs afoul of many companies' software policies? And will be blocked by many companies even if it doesn't run afoul of their policies because nearly every competently run company will inspect software that claims to have AI features to understand the extent of the AI integration, but a significant portion of them will choose not to do that analysis for what's a fairly niche software that not only has many alternatives but is an alternative to an OSX built in feature and would block many of your users from using the application.

Even if you disagree with the ideological dissensions, and even if you disagree with the slippery slope argument, why would you grumble about the practical scenario which would block your users from using the application. Especially when you have a fairly easy alternative of packaging it in a plugin.

[galad87]

I wonder how those companies will deal with the upcoming AI features in Windows and macOS.

[leetcrew]

apple and microsoft have historically provided ways of turning off features that their corporate customers don't want. I doubt this will be any different.

[galad87]

iTerm AI feature was off by default and you had to manually insert a valid key, but it seems it was still an issue.

[wpm]

The change notes nor the UI do not imply this.

All this needs was a single checkbox “Disable OpenAI Integration” or codecierge or whatever it’s called. A single, unequivocal “this is not enabled” signal to the user who does not want or cannot what this feature enabled.

[adamomada]

But how is that different from a UI which is the equivalent of a “enable openai integration” checkbox??

You needed the word “Disable” in there?

[wpm]

Yes? Or maybe my CISO does?

These things should be as unambiguous as the "webcam is on" LED.