iTerm2 3.5.0

Original Article ↗ Hacker News Discussion ↗

iTerm2’s 3.5.0 release for macOS introduces optional AI-powered command generation and an OpenAI-integrated “Codecierge” assistant, alongside more traditional terminal improvements like better tmux integration and OSC 52 clipboard support. Commenters are sharply split: some welcome AI help for complex shell workflows or plan to point it at local LLMs, while others are alarmed by the idea of any terminal tooling that can stream output to external models, citing privacy, compliance, and “AI-everywhere” fatigue. Alternative terminals such as WezTerm, Alacritty, and the upcoming Ghostty are highlighted by those wary of integrating generative AI into core developer tools.

AI features & behavior

  • 3.5.0 adds two main LLM features:
    • “Engage AI” (Cmd+Y): user types a natural-language request; iTerm returns shell commands in a small pane; user must explicitly paste/run them.
    • “Codecierge” in the Toolbelt: can watch terminal output and guide the user toward a goal; optionally can “run commands automatically,” with strong warnings about risk.
  • Both require the user to supply an OpenAI API key; no key → features don’t function.
  • Default prompt focuses on returning copy‑pasteable shell commands without extra commentary.

Privacy, security, and compliance concerns

  • Many commenters are uneasy about any AI integration in a terminal, especially with an option to stream “everything that happens” to OpenAI.
  • Some argue this is unacceptable for confidential work or regulated environments (HIPAA/SOC2, enterprise security policies).
  • Others counter that:
    • The feature is strictly opt‑in and can’t work without a user-supplied key.
    • Network controls/firewalls are the real enforcement layer.
    • Source code is available for audit.
  • Concern that junior staff may feel pressured to enable AI to “keep up,” creating organizational risk.

Local models and configuration UX

  • iTerm allows configuring a custom “URL for AI API” in Advanced settings, enabling OpenAI‑compatible local services (e.g., Ollama), though support for some setups is only in the next/beta release.
  • Several users found the AI settings discoverability and lack of an explicit “enable/disable” checkbox confusing.
  • Debate over whether updater/release notes made AI changes sufficiently clear.

Attitudes toward AI in terminals

  • Supporters see clear utility: generating jq/awk/ffmpeg commands, explaining obscure errors, and avoiding context‑switching to a browser.
  • Critics see “AI everywhere” as gimmicky, risky, or philosophically wrong for terminals, and some plan to avoid or pin older versions.

Other notable features & general reception

  • Non‑AI improvements appreciated: better shell integration behavior for long outputs, OSC 52 clipboard support (good with Neovim 0.10), tmux control‑mode integration, leader key support, and continued overall polish.
  • iTerm2 is widely praised as feature‑rich, stable, and donation‑worthy, though some prefer simpler/faster terminals.

Alternatives & ecosystem

  • Alternatives mentioned: WezTerm (frequently praised), Alacritty, Kitty, Ghostty (private beta), Prompt, and stock Terminal.app.
  • Some users consider switching specifically to avoid any AI hooks; others view the backlash as overblown given the optional nature.