iTerm 3.5.1 removes automatic OpenAI integration, requires opt-in

Original Article ↗ Hacker News Discussion ↗

iTerm2’s new OpenAI-powered terminal assistance, originally shipped as an opt‑in feature requiring a user API key, triggered intense backlash over privacy, security, and the growing trend of bundling AI into core tools. Commenters argue over whether moving the integration into a separately blockable plugin and adding “impenetrable firewall” settings meaningfully improves corporate compliance, or merely represents security theater to appease an anti‑AI mob. The episode also raises broader concerns about entitlement toward open‑source maintainers and how easily small, vocal groups can pressure project roadmaps.

Scope of the Change

  • Original AI feature was already opt‑in and required:
    • Manually enabling in settings.
    • Supplying an API key.
    • Explicit user action (invoking a UI, submitting a prompt).
  • 3.5.1 adds “safety valves”:
    • Makes AI functionality more clearly optional/configurable.
    • Separates network-calling code into a plugin/extra binary.
    • Allows stricter disabling for regulatory/MDM/corporate needs.

Corporate and Security Concerns

  • Some argue any built‑in “can send data out” feature makes tools non‑deployable in strict environments unless:
    • It can be centrally disabled via policy/MDM.
    • Or it is fully separable/blocked at install level.
  • Others counter:
    • Serious orgs already block AI endpoints at the network level; app-level toggles are secondary.
    • A terminal can already exfiltrate data via curl, SSH, etc., so focusing on this feature is inconsistent.
  • Disagreement on security impact of moving AI calls to a separate binary:
    • One side: better containment and compliance.
    • Other side: more attack surface / less-scrutinized helper, arguably worse security theater.

Backlash and Open Source Dynamics

  • Many feel the outrage was disproportionate for an optional feature:
    • Claims of misinformation (e.g., “it will secretly send all data”).
    • Reports of dogpiling, harassment, and even violent rhetoric off-site.
  • Others say:
    • There were legitimate corporate/compliance concerns mixed in.
    • Users are allowed to object to design directions even in free software.
  • Several comments worry this kind of backlash contributes to maintainer burnout and discourages OSS work.

Attitudes Toward AI in Tools

  • Split views:
    • Some see AI-in-terminal as a great fit (e.g., generating find commands).
    • Others dislike the presence of AI at all, preferring no possibility of data leaving the terminal.
    • Some are broadly pro‑AI but found the UX clunky (mouse clicks, modal dialog) and therefore not worth using.

iTerm2 vs Alternatives & Ecosystem

  • Multiple users reiterate strong appreciation for iTerm2’s features (tmux integration, splits, triggers, layouts, search, etc.).
  • Some switched to other terminals (e.g., Kitty, WezTerm, macOS Terminal) over the AI feature or performance preferences.
  • A few suggest Apple and large companies should financially support widely used macOS OSS tools.