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.
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.
You needed the word “Disable” in there?
These things should be as unambiguous as the "webcam is on" LED.