iTerm2 removes AI feature from core, creates separate plugin

Original Article ↗ Hacker News Discussion ↗

Nature of the AI Feature & Misunderstandings

  • AI integration was opt‑in and required providing an API key; several commenters stress it does nothing until explicitly invoked via a separate toolbox.
  • Others argue that “unconfigured” is not the same as “disabled”: any non‑empty API key field (even a stray space) could enable the capability, and there was no explicit master toggle.
  • Some reports claimed all keystrokes were being sent to OpenAI; defenders say these were based on tests with invalid keys and misrepresented packet captures.

Security, Privacy, and Organizational Constraints

  • One camp sees minimal new risk: a terminal can already spawn arbitrary processes or use tools like SSH/curl to exfiltrate data.
  • Another camp argues that any baked‑in network/LLM path in a terminal is unacceptable, especially where secrets are handled; “minimization over hardening” is cited.
  • Organizations with blanket AI bans might block iTerm if AI is in core, regardless of technical details, due to limited security review capacity.
  • Some say such orgs should rely on MDM/firewalls; others counter that’s unrealistic given resource constraints.

Core vs Plugin & Product/UX Decisions

  • Many argue the AI feature should have been a separate plugin from the start, aligning with expectations that plugins are explicitly installed/activated.
  • Others note there is little technical difference between core and plugin, but concede the social/organizational signaling is important.
  • Onboarding that prominently surfaced the AI feature likely amplified emotional backlash.

Open‑Source Dynamics & Community Behavior

  • Multiple commenters describe the backlash as toxic, entitled, and demoralizing, citing insults, misinformation, and even violent rhetoric.
  • Others say mistrust is understandable given wider industry behavior and see the move to a plugin as “the right product decision,” not just appeasement.

Attitudes Toward AI & Terminal Philosophy

  • Some find integrated AI genuinely useful for constructing complex commands (ffmpeg, ImageMagick, shell scripting).
  • Others view terminals as conservative tools where “shiny” features (AI, NFTs, etc.) don’t belong and prefer minimalist alternatives (e.g., Alacritty, Kitty).
  • Broader AI fatigue is evident: many are tired of AI being added everywhere, even where perceived benefit is low.