HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gnachman
iTerm2
Swift2011–2026
gnachman / iTerm2

iTerm2

iTerm2 is a terminal emulator for Mac OS X that does amazing things.

32Distinct people
44Mentions
0Explicit recommenders
18.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

iTerm2 is a terminal emulator for Mac OS X that does amazing things.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:49:33 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year44 dated mentions

Observed mentions: 2011-12-20 18:48:52 UTC to 2026-09-05 15:55:18 UTC.

0369122011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC101
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC101
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC303
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC11011
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC606
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC505

What Hacker News says

11 sources
The correct response to false allegations followed by insults and threats is anything but to admit it. The software in question is a popular free and open source software that has more than a decade of trust. The AI feature fundamentally requires the user to actively engage with in order to use it [1], with no nagging or coercion whatsoever. In fact, the only people reminding us of its existence are the Mastodon mobs, not iTerm. The feature wasn't added out of pure hype either. It was likely inspired by user feedback [2], and the dev ultimately added it because it was useful for him personally [3]. Despite all of this, people are raging about unprovable nefarious motives and making claims about spyware, as if it's Windows we're talking about. They pretend as if it's maintained by some faceless for-profit entity trying to screw us over ins
Read the rest
tead of a sole developer trying to create good software in his spare time. Some are even openly fantasizing about inflicting physical violence [4]. This kind of behavior should be condemned, not praised. [1]: https://github.com/gnachman/iTerm2/blob/a3122c0100d8900a15cb... [2]: https://gitlab.com/gnachman/iterm2/-/issues/6955 [3]: https://techhub.social/@gnachman/109542492387391561 [4]: https://web.archive.org/web/20240613165712/https://archive.i...
In iTerm2 v3.5.1 moves AI features into external plugin
Don't overlook the awesome "automatically bury session" option, which hides the "actual" iTerm2 window running the tmux control plane: https://iterm2.com/documentation-buried-sessions.html and this is the preference I mean: https://github.com/gnachman/iTerm2/blob/v3.5.2/Interfaces/Pr... I also have dedicated .ssh/config entries for ensuring that ssh connects directly to tmux: Host whatever-mux Hostname whatever RequestTTY yes RemoteCommand /usr/bin/tmux -u -CC att
In Show HN: Shpool, a Lightweight Tmux Alternative
Entering an API key doesn't immediately cause iTerm to start send data to OpenAI. That's a straight up lie started by people who actually tested the feature and posted their findings on the GitLab thread [1][2] about it. OpenAI integration is activated after you write a question to be sent to the AI [3]. It takes many clicking and typing to get to that point and can't possibly happen by accident. It's one thing to not like a feature. But to behave in the way people behaved is not merely ridiculous, it's wrong and horrifying. People came to the issue tracker from Mastodon looking to start a fight that was uncalled for, threw insults and lies, and fantasized about physically harming the dev [4]. When all they could've done to avoid the feature was to simply do nothing. [1]: https://gitlab.com/gnachman/iterm2/-/issues/11475 [2]: https://gitl
Read the rest
In iTerm2 v3.5.1 moves AI features into external plugin
Now you ignored everything past the first four words of what I quoted. It doesn't "meddle or leak" your terminal data. OpenAI integration only kicks in after explicit user action. Looking at the screenshots, it appears to only become active for the current terminal pane. https://github.com/gnachman/iTerm2/blob/master/images/Onboar... Also, iTerm is developed by an actual respect-worthy person who actually cares about this kind of stuff, not by an "AI overlord." It's unfortunate that you instantly chose to make baseless spyware accusations in public forums instead of supporting him for creating the software that you've relied on.
In iTerm 3.5.1 removes automatic OpenAI integration, requires opt-in
> iTerm 3.5.1 removes automatic OpenAI integration, requires opt-in This is an editorialized title. It was opt-in from the very beginning. Here's all the steps that was originally required: 1. Open settings, go to the General tab, click on the AI button. 2. Enter a paid API key 3. Close the settings 4. Click "Toolbelt" on the menu bar, and click on "Codecierge" 5. Click "Toolbelt" on the menu bar again, and click "Show toolbelt" 6. In the toolbelt, there's a textbox that you can type questions into. The textbox won't be shown if you didn't enter an API key. Only after submitting the question will the OpenAI integration be activated, and as I understand it, only for the current session. https://github.com/gnachman/iTerm2/blob/a3122c0100d8900a15cb... The initial implementation already took many many clicks to run. I literally had to do noth
Read the rest
ing to not use the feature and not once was I reminded about the feature after I chose to ignore it. Despite that, people were spreading rumors that entering an invalid API key would instantly cause iTerm to send all data to OpenAI. It's a straight up lie started by people who actually tested the feature and posted their findings on the GitLab thread about this feature. https://gitlab.com/gnachman/iterm2/-/issues/11475 https://gitlab.com/gnachman/iterm2/-/issues/11470 It gets worse, people in the GitLab thread were calling for dogpiles and fantasizing about inflicting violence on Mastodon. Towards the sole maintainer of a popular free and open source software developed in his spare time. https://web.archive.org/web/20240613165712/https://archive.i... Some of the things you see online... I have no words.
In iTerm 3.5.1 removes automatic OpenAI integration, requires opt-in
If you're so paranoid about this possibility then just block it at the network level - heck, even whitelist IP ranges that you want iTerm2 to be able to connect out to and default deny the rest. Let's not blame iTerm2, which is a highly useful, amazing piece of software that many of us have relied on on every day for years and have never paid anything to use. If you really are so worried about the AI feature being part of iTerm2 then go fork it and strip the AI functionality yourself: https://github.com/gnachman/iTerm2
In iTerm2 feature request: disable all AI-related features
I tried it but I get an error: "There was a problem with the AI query: Error from OpenAI: [] is too short - 'messages'" According to the docs it only uses that if the model doesn't begin tieh gpt- and uses an old API, so alas it doesn't seem compatible with ollama. Edit: here is the relevant part of the code: https://github.com/gnachman/iTerm2/blob/a196d31658a8d0aa2dc5... Looks like adding ollama support is really a matter of changing a few lines of code. Edit 2: Seems to be fixed in the next beta release: https://github.com/gnachman/iTerm2/commit/fcd212490626f1d8ea...
In iTerm2 and AI Hype Overload
Have you used iTerm2? Saw the amount of work that's put into it? Checked how long it has been cared for, maintained, and continuously improved on by basically one person for more than a decade? All for free and no ads? The iTerm2 developer is a person you can actually trust. https://github.com/gnachman/iTerm2/graphs/contributors But all of a sudden you now have people up in arms about how a spyware of a feature was sneakily forced upon them, and be righteous about it. This is sad.
In iTerm2 3.5.0
For macOS users, iTerm2 offers the exact same feature [1][2] since v3.5.0beta9 (Dec 19, 2022). Both Shelly [3] and iTerm use OpenAI under the hood. Here are several alternatives [4]. [1] https://github.com/gnachman/iTerm2/commit/7bcc4e0bedb22c4fd9... [2] https://cixtor.com/blog/iterm2-openai [3] https://github.com/paletov/shelly/blob/main/src/llm_service.... [4] https://github.com/search?q=terminal+chatgpt&type=repositori...
In Show HN: Shelly: Write Terminal Commands in English

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.