iTerm2 vs Alacritty

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   iTerm2—none0/10

   Probes explicitly show no llms.txt or machine-readable/agent-oriented docs endpoint exists (404s), and no other evidence indicates agent-oriented documentation formats are offered.

   • [probe] “PROBE llms.txt: HTTP 404 at https://iterm2.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://iterm2.com/documentation.html.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://iterm2.com/openapi.json, https://iterm2.com/swagger.json, https://iterm2.com/api/openapi.jso…”

   proof ↗⚑ flag

   Alacritty—none0/10

   Alacritty is a terminal emulator with no llms.txt or agent-oriented documentation; a direct probe confirms llms.txt returns 404 and no OpenAPI/agent docs exist.

   • [probe] “PROBE llms.txt: HTTP 404 at https://alacritty.org/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://alacritty.org/openapi.json, https://alacritty.org/swagger.json, https://alacritty.org/api/op…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   iTerm2—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   iTerm2—none0/10

   iTerm2 has an AI chat plugin and Python scripting API, but no evidence anywhere in the pack of MCP server integration or ability to plug in MCP tools. This is a plausible axis for a terminal with AI features, but absent evidence it defaults to none.

   ⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   iTerm2—none0/10

   No evidence of an official MCP server for iTerm2; it offers an AI chat plugin (OpenAI-based) and Python/AppleScript scripting APIs, but nothing about MCP protocol support. Probes for docs/API specs also return 404s.

   • [claimed-docs] “This is an optional component you can install to enable generative AI features in iTerm2.”
   • [github] “Built-in LLM chat window that can optionally interact with terminal contents. Link sessions to get context-aware help, run commands on your …”
   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://iterm2.com/llms.txt”

   proof ↗⚑ flag

   Alacritty—none0/10

   This product is not itself an agent, so publishing an official MCP server is plausible and the axis applies; no first-party MCP server appears in the evidence. (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Alacritty
   iTerm2~partialprobed4/10

   iTerm2 ships official automation surfaces — a Python scripting API and AppleScript support (iterm2-docs-13, iterm2-docs-14, iterm2-gh-15) — and community reports mention bundled command-line utilities like imgcat and it2dl for scripting terminal interactions (iterm2-comm-5, iterm2-comm-6), which could serve AI-native/agentic automation. However none of this constitutes a dedicated, documented 'official CLI' tool designed for agentic/AI-native control (e.g., no `iterm2` command-line binary with subcommands is described), and probes for machine-readable API docs (llms.txt, openapi.json) all 404 (iterm2-probe-1, iterm2-probe-3). Missing for 10: a first-party CLI binary/tool explicitly documented for scripting/automation, official docs framing it for AI-agent use, and independent confirmation of CLI-driven agentic workflows.

   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”
   • [community] “"Along with imgcat there's it2dl. Downloads a file from the remote system browser-style. It's much more convenient than scp, especially when…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://iterm2.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://iterm2.com/openapi.json, https://iterm2.com/swagger.json, https://iterm2.com/api/openapi.jso…”

   proof ↗⚑ flag

   Alacritty✓fullclaimed6/10

   Alacritty ships an official CLI: the `alacritty` binary itself plus documented subcommands like `alacritty msg create-window` for IPC control, which any script or agent can invoke non-interactively. Missing for 10: no AI-agent-specific documentation, no broader scripting/automation API beyond window creation/message IPC, and no independent corroboration of AI-driven usage.

   • [claimed-docs] “New windows can be created either by using the `CreateNewWindow` keybinding action, or by executing the `alacritty msg create-window` subcom…”
   • [claimed-docs] “Offer IPC using _alacritty msg_”
   • [claimed-docs] “Offer IPC using alacritty msg”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to iTerm2
   iTerm2✓fullprobed8/10

   iTerm2 documents a full Python API (iterm2 package) for scripting/controlling the app, plus AppleScript support, both with dedicated documentation pages and community corroboration of hands-on use (imgcat, it2dl, Python scripting praised as far superior to AppleScript). This constitutes a documented public API for programmatic/agentic control, though it's not a modern REST/OpenAPI-style API and no llms.txt/OpenAPI spec exists. Missing for 10: a formal OpenAPI/REST-style spec or llms.txt discoverability layer, and no evidence of AI-agent-specific SDK usage beyond scripting.

   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://iterm2.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://iterm2.com/openapi.json, https://iterm2.com/swagger.json, https://iterm2.com/api/openapi.jso…”

   proof ↗⚑ flag

   Alacritty~partialprobed4/10

   Alacritty documents a limited IPC surface via `alacritty msg` (e.g. create-window, config reload) that could be scripted by an external agent, but this is a narrow CLI/IPC mechanism rather than a full documented public API, and explicit probes show no OpenAPI spec or llms.txt endpoint exists. missing for 10: a comprehensive API reference (REST/RPC/plugin API), machine-readable API spec (OpenAPI/llms.txt), and evidence of AI/agent tooling built against it.

   • [claimed-docs] “Offer IPC using _alacritty msg_”
   • [claimed-docs] “Offer IPC using alacritty msg”
   • [claimed-docs] “New windows can be created either by using the `CreateNewWindow` keybinding action, or by executing the `alacritty msg create-window` subcom…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://alacritty.org/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://alacritty.org/openapi.json, https://alacritty.org/swagger.json, https://alacritty.org/api/op…”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   iTerm2—none0/10

   No evidence of any webhook subscription mechanism; iTerm2 offers triggers and a Python scripting API for local automation but nothing about outbound webhook events or subscriptions is documented.

   ⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to iTerm2
   iTerm2~partialcommunity5/10

   iTerm2 supports regex-based Triggers that autonomously fire actions (highlighting, running commands, notifications, invoking Python scripts) when patterns appear, and offers a full Python scripting API for background automation and custom features [iterm2-docs-16, iterm2-gh-2, iterm2-docs-13, iterm2-gh-15]. This provides generic background automation but isn't framed around AI-agent workflows specifically. missing for 10: evidence of AI-driven or agentic automations running unattended, scheduling/cron-like persistent background tasks tied to AI features, and independent confirmation that these automations run reliably without user oversight.

   • [claimed-docs] “iTerm2 supports user-defined triggers, which are actions that run when text matching a regular expression is received.”
   • [github] “Triggers - Regex patterns that fire actions when matched: highlight text, run commands, send notifications, open password manager, set marks…”
   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”

   proof ↗⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

Api quality

1. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   iTerm2—none0/10

   iTerm2 offers a Python scripting API but no evidence of a downloadable OpenAPI/machine-readable API spec; explicit probes for llms.txt, docs-md, and openapi.json all returned 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://iterm2.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://iterm2.com/documentation.html.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://iterm2.com/openapi.json, https://iterm2.com/swagger.json, https://iterm2.com/api/openapi.jso…”
   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”

   proof ↗⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

Ai agent

1. ai-native userDelegate terminal tasks to a built-in AI agent that plans and executes commands with my approval

   weight 3 · round to iTerm2
   iTerm2~partialcommunity5/10

   iTerm2 ships an optional AI plugin providing a built-in LLM chat that can be linked to a session to give context-aware help, explain output, and 'run commands on your behalf' (iterm2-docs-15, iterm2-gh-6), which is a real but thin form of AI-agent delegation. However, there's no documented explicit plan-then-approve workflow (e.g., showing a command and requiring confirmation before execution), and community reports raise concerns that the AI toggle's off/on state was ambiguous, undermining confidence in a clean approval gate (iterm2-comm-1, iterm2-comm-2). Missing for 10: documented step-by-step approval/confirmation UI before command execution, evidence of autonomous multi-step planning, and independent hands-on validation that the agent respects user approval before running commands.

   • [claimed-docs] “This is an optional component you can install to enable generative AI features in iTerm2.”
   • [github] “Built-in LLM chat window that can optionally interact with terminal contents. Link sessions to get context-aware help, run commands on your …”
   • [community] “"It takes much less effort for me to simply switch back to Terminal.app." (reacting to iTerm2 adding an opt-in OpenAI-based AI feature)”
   • [community] “Users reported that iTerm2's new AI feature wasn't a true disabled toggle: "Put anything in the box for the OpenAI key, valid or not, and th…”

   proof ↗⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

Ai privacy

1. ai-native userUse or fully disable AI features with clear control over what session data leaves my machine, without a forced login

   weight 2 · round to iTerm2
   iTerm2!disputedcontradicted5/10

   iTerm2 ships AI chat as an optional, install-only plugin with no forced login (iterm2-docs-15, iterm2-gh-6), suggesting users can ignore or avoid it entirely. However, hands-on community reports concretely contradict 'clear control': a user found that merely putting any text (even a stray space) in the API key field silently activates data-sending to OpenAI, with no reliable way to see the feature is actually disabled (iterm2-comm-2), and another reacted by switching terminals entirely over trust concerns (iterm2-comm-1). Missing for 10: no documentation on exactly what session data leaves the machine when AI chat is enabled, no fix/acknowledgment of the toggle bug, and no independent verification that the issue was resolved.

   • [claimed-docs] “This is an optional component you can install to enable generative AI features in iTerm2.”
   • [github] “Built-in LLM chat window that can optionally interact with terminal contents. Link sessions to get context-aware help, run commands on your …”
   • [community] “"It takes much less effort for me to simply switch back to Terminal.app." (reacting to iTerm2 adding an opt-in OpenAI-based AI feature)”
   • [community] “Users reported that iTerm2's new AI feature wasn't a true disabled toggle: "Put anything in the box for the OpenAI key, valid or not, and th…”
   • [community] “Some users called the backlash overblown: "a feature that is inactive by default, consumes no processing power, memory or anything else" sti…”

   proof ↗⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

1. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to iTerm2
   iTerm2✓fullclaimed8/10

   iTerm2 supports user-defined Triggers that fire on regex matches from terminal output, enabling automatic actions like highlighting, running commands, sending notifications, invoking Python scripts, or opening a password manager — a documented rules-on-event automation system, further extensible via the Python API for custom triggers/behaviors. missing for 10: no independent hands-on validation of complex trigger chains, and no evidence of AI-specific event-triggering beyond generic regex triggers.

   • [claimed-docs] “iTerm2 supports user-defined triggers, which are actions that run when text matching a regular expression is received.”
   • [github] “Triggers - Regex patterns that fire actions when matched: highlight text, run commands, send notifications, open password manager, set marks…”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”
   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”

   proof ↗⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

2. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   iTerm2—none0/10

   iTerm2 offers triggers, Python scripting API, and AppleScript automation, but there is no evidence of a scheduler or mechanism for recurring/cron-like jobs or workflows; automation is event-triggered or manually scripted, not scheduled.

   ⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

3. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   iTerm2—none0/10

   No evidence of any version control, review, or rollback mechanism for automations (triggers, Python scripts, profiles). iTerm2 supports scripting and triggers, but nothing in the evidence pack shows versioning, diffing, review workflows, or rollback of these automations.

   ⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

Dotfiles

1. power-userKeep the terminal's full configuration as plain-text files in my dotfiles and sync it across machines

   weight 3 · round to Alacritty
   iTerm2—none0/10

   The evidence pack contains no mention of iTerm2's preferences file format, exporting/importing settings as plain-text/plist files, or any dotfiles-style sync workflow across machines. Without evidence for this specific capability, it cannot be credited even though it is a plausible axis for a terminal emulator.

   ⚑ flag

   Alacritty✓fullclaimed9/10

   Alacritty's config is a plain-text TOML file that supports importing additional files (great for dotfiles modularity), making it straightforward to version-control and sync across machines. Docs explicitly confirm TOML format and file import support. Missing for 10: no explicit community testimonial about dotfiles syncing workflow specifically.

   • [claimed-docs] “Alacritty's configuration file uses the TOML format.”
   • [claimed-docs] “Import additional configuration files.”
   • [claimed-docs] “Import additional configuration files. Imports are loaded in order, skipping all missing files, with the importing file being loaded last.”

   proof ↗⚑ flag

Fonts

1. developerUse programming fonts with ligatures, fallback fonts, and fine-grained font tuning

   weight 2 · round drawn
   iTerm2—none0/10

   The evidence pack contains no mention of font rendering, ligature support, fallback fonts, or font-tuning settings anywhere in iTerm2's docs, GitHub feature list, or community discussion; only general 'mind-boggling number of options' and color-mode claims are present, which don't address fonts specifically. Missing for 10: any mention of font selection, ligature support, fallback font configuration, or font-size/spacing tuning options.

   ⚑ flag

   Alacritty—none0/10

   Community evidence explicitly states Alacritty lacks ligature support ('the classic ligature issue... given up hope there will ever be support') and no docs mention fallback-font configuration; only basic letter/line-spacing tuning (docs-33) is evidenced, which is insufficient to satisfy the combined ligatures+fallback+font-tuning story.

   • [community] “Ah! The 'classic' ligature issue. Have been following that for a while. Kind of given up hope that there will ever be any support for it.”
   • [claimed-docs] “Offset is the extra space around each character. _y_ can be thought of as modifying the line spacing, and _x_ as modifying the letter spacin…”

   proof ↗⚑ flag

Theming

1. power-userApply color schemes and themes, including automatic light/dark mode switching

   weight 2 · round to Alacritty
   iTerm2—none0/10

   The evidence pack contains no mention of color schemes, themes, or automatic light/dark mode switching for iTerm2 despite this being a plausible and well-known capability for a terminal emulator; no docs, GitHub, or community citations address theming at all. missing for 10: any documentation or mention of color scheme/theme support, dark mode toggling, or automatic OS appearance syncing.

   ⚑ flag

   Alacritty~partialclaimed3/10

   Alacritty's TOML config lets users define custom colors via hex codes and import additional config files, which the community uses to build/swap color schemes, but there is no documented built-in mechanism for named themes or automatic OS light/dark mode switching. missing for 10: official theme gallery/switcher, automatic light/dark detection, live reload without restart for such changes.

   • [claimed-docs] “Colors are specified using their hexadecimal values with a # prefix: #RRGGBB.”
   • [claimed-docs] “Colors are specified using their hexadecimal values with a _#_ prefix: _#RRGGBB_.”
   • [claimed-docs] “Import additional configuration files.”
   • [claimed-docs] “Import additional configuration files. Imports are loaded in order, skipping all missing files, with the importing file being loaded last.”
   • [claimed-docs] “Live config reload (changes require restart)”
   • [claimed-docs] “Live config reload (changes require restart) Default: true”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to iTerm2
   iTerm2~partialprobed6/10

   iTerm2's Python API is documented as controlling and extending iTerm2 behavior (custom status bar, triggers, menu items, session control), and a community hands-on review calls it able to 'touch pretty much everything' via scripting, which supports broad API-driven control. However, there's no evidence of a formal claim or documentation of full UI/API parity — no explicit list mapping every UI feature (e.g. AI chat, browser profiles, tmux integration) to API equivalents, and probes show no OpenAPI spec or llms.txt for verifying coverage. Missing for 10: explicit parity documentation, API coverage for newer UI features (AI chat, browser profiles), and independent verification that all UI actions are scriptable.

   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://iterm2.com/openapi.json, https://iterm2.com/swagger.json, https://iterm2.com/api/openapi.jso…”

   proof ↗⚑ flag

   Alacritty~partialclaimed2/10

   Alacritty offers a limited IPC via `alacritty msg` for actions like creating new windows and reloading config, but the vast majority of UI-driven features (vi mode navigation, search, selection, mouse interactions, hints) have no documented API/CLI equivalent. missing for 10: API parity for search/selection/vi-mode/mouse actions, documented full IPC command reference, evidence of programmatic control beyond window creation/config reload.

   • [claimed-docs] “New windows can be created either by using the `CreateNewWindow` keybinding action, or by executing the `alacritty msg create-window` subcom…”
   • [claimed-docs] “Offer IPC using _alacritty msg_”
   • [claimed-docs] “Offer IPC using alacritty msg”
   • [claimed-docs] “The vi mode allows moving around Alacritty's viewport and scrollback using the keyboard.”
   • [claimed-docs] “Search allows you to find anything in Alacritty's scrollback buffer.”
   • [claimed-docs] “Terminal hints allow easily interacting with visible text without having to start vi mode.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   iTerm2—none0/10

   No evidence of any data export feature or open-format export for iTerm2's own data (settings, session history, paste history, profiles); the evidence pack instead shows probes for llms.txt/openapi returning 404s and no mention of export/portability tooling. missing for 10: documented export of preferences/profiles/history in open formats, data portability guarantees, migration/export tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://iterm2.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://iterm2.com/documentation.html.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://iterm2.com/openapi.json, https://iterm2.com/swagger.json, https://iterm2.com/api/openapi.jso…”

   proof ↗⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Alacritty
   iTerm2~partialclaimed6/10

   The evidence repeatedly cites a public GitHub repository (github.com/gnachman/iTerm2) as the canonical source for iTerm2's features, indicating the source code is publicly hosted and readable. However, none of the evidence explicitly states or links to a specific open-source license (e.g., GPL) or license file, so the 'open license' claim is not directly confirmed. Missing for 10: explicit license identification/text, documentation page confirming licensing terms, independent confirmation of license compliance.

   • [github] “Browser profiles integrate web browsing into iTerm2's window/tab/pane hierarchy. Copy mode, triggers, AI chat, and other terminal features w…”
   • [github] “Session Restoration - Sessions run in long-lived server processes. If iTerm2 crashes or upgrades, your shells keep running. When iTerm2 rest…”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”

   proof ↗⚑ flag

   Alacritty✓fullclaimed9/10

   Alacritty is a well-known open-source project hosted publicly on GitHub under an open license (BSD/Apache-style, common knowledge reinforced by the repo being the canonical source referenced throughout docs), with source, install instructions (cargo build/install), and INSTALL.md all publicly accessible. missing for 10: explicit citation of the LICENSE file text/name in the evidence pack.

   • [github] “The supported platforms currently consist of BSD, Linux, macOS and Windows.”
   • [claimed-docs] “cargo build --release”
   • [claimed-docs] “cargo install alacritty”
   • [claimed-docs] “If you're just interested in the Alacritty binary and you don't need the terminfo file, desktop entry, manual page or shell completions, you…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   iTerm2—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

   Alacritty—none0/10

   The axis applies to terminal emulators as a kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/terminals-na-harmonize.ts.)

   ⚑ flag

Multiplexing

1. developerSplit windows into panes and organize work across tabs without an external multiplexer

   weight 3 · round to iTerm2
   iTerm2✓fullclaimed9/10

   iTerm2 natively supports splitting tabs into multiple panes (vertical/horizontal) and organizing sessions across tabs and windows, directly replacing the need for tmux/screen for basic pane-and-tab workflows, with session restoration and profile-based organization further supporting this. missing for 10: independent hands-on verification specifically of pane-splitting workflow (community evidence focuses on other features like imgcat/scripting rather than confirming multiplexing usability directly).

   • [claimed-docs] “Divide a tab up into multiple panes, each one showing a different session. You can slice vertically and horizontally”
   • [claimed-docs] “Divide a tab up into multiple panes, each one showing a different session.”
   • [github] “Session Restoration - Sessions run in long-lived server processes. If iTerm2 crashes or upgrades, your shells keep running. When iTerm2 rest…”
   • [claimed-docs] “iTerm2 provides a taggable and searchable profiles database so you can easily find the profile you're looking for.”
   • [claimed-docs] “you can define a profile that's always used when you ssh to some hostname. Or when your username is root. Or even when you're in a particula…”

   proof ↗⚑ flag

   Alacritty—none0/10

   Alacritty's own GitHub docs explicitly state it does not support tabs or splits, deferring that to a window manager or terminal multiplexer, and community feedback confirms the lack of tabs was a dealbreaker for some users.

   • [github] “This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer)”
   • [community] “I used to use kitty, but its CPU usage was on the higher side. I tried alacritty but the lack of tabs was a deal-breaker, so I switched to W…”

   proof ↗⚑ flag

Quick access

1. power-userSummon the terminal instantly with a global hotkey or quake-style dropdown window

   weight 1 · round to iTerm2
   iTerm2✓fullclaimed9/10

   Docs explicitly describe a global hotkey to bring iTerm2 to the foreground from any app, and GitHub evidence confirms a quake-style dropdown that slides down from a screen edge, even over fullscreen apps. Missing for 10: independent hands-on user testimonial specifically praising the hotkey/dropdown window feature.

   • [claimed-docs] “Register a hotkey that brings iTerm2 to the foreground when you're in another application. A terminal is always a keypress away.”
   • [claimed-docs] “Register a hotkey that brings iTerm2 to the foreground when you're in another application.”
   • [github] “System-wide hotkey summons a terminal that slides down from the top of the screen (or any edge), even over fullscreen apps.”

   proof ↗⚑ flag

   Alacritty—none0/10

   No evidence of a global hotkey summon or quake-style dropdown window feature; Alacritty explicitly omits window-management features like tabs/splits, leaving such behavior to external tools (window managers/multiplexers), and no dropdown/hotkey capability is documented.

   • [github] “This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer)”

   proof ↗⚑ flag

Sessions

1. developerRestore my windows, tabs, and working directories after a restart or crash

   weight 2 · round to iTerm2
   iTerm2✓fullclaimed8/10

   Session restoration via long-lived server processes reconnects shells (including working directories via shell integration) after crash/restart, and tmux -CC integration persists windows/tabs/panes even when iTerm2 or the SSH session drops. Missing for 10: no independent/hands-on confirmation of restoring exact tab/pane layout after a full app crash, only vendor/docs claims.

   • [github] “Session Restoration - Sessions run in long-lived server processes. If iTerm2 crashes or upgrades, your shells keep running. When iTerm2 rest…”
   • [github] “Sessions run in long-lived server processes. If iTerm2 crashes or upgrades, your shells keep running. When iTerm2 restarts, it reconnects to…”
   • [github] “Sessions run in long-lived server processes. If iTerm2 crashes or upgrades, your shells keep running.”
   • [claimed-docs] “When you run "tmux -CC", a new tmux session is created. An iTerm2 window opens and it acts like a normal iTerm2 window. The difference is th…”
   • [claimed-docs] “When iTerm2 quits or the ssh session is lost, tmux keeps running. You can return to the host you were ssh'ed into and run "tmux -CC attach" …”
   • [claimed-docs] “iTerm2 may be integrated with the unix shell so that it can keep track of your command history, current working directory, host name, and mo…”
   • [claimed-docs] “iTerm2 can integrate with your shell so it knows where your shell prompt is, what commands you're entering, which host you are on, and what …”

   proof ↗⚑ flag

   Alacritty—none0/10

   Alacritty explicitly does not implement tabs or splits, delegating such functionality to a window manager or multiplexer, and there is no evidence of any session/window/working-directory restoration feature after crash or restart.

   • [github] “This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer)”
   • [community] “I used to use kitty, but its CPU usage was on the higher side. I tried alacritty but the lack of tabs was a deal-breaker, so I switched to W…”

   proof ↗⚑ flag

Benchmarks

1. power-userSee published benchmarks or measured latency/throughput numbers backing the terminal's performance claims

   weight 2 · round to Alacritty
   iTerm2—none0/10

   No evidence pack item presents published benchmarks, latency/throughput numbers, or any measured performance data for iTerm2; the material covers features (panes, tmux integration, scripting) and unrelated community discussion (AI feature controversy, a security disclosure) with no performance metrics whatsoever.

   ⚑ flag

   Alacritty~partialcommunity5/10

   Alacritty's GitHub README explicitly cites use of vtebench to quantify terminal throughput and claims it consistently outperforms competitors, and community anecdotes (HN threads) corroborate a perception of superior speed (e.g. faster startup than kitty, faster than iTerm2/Terminal in a `find` test). However, no actual published benchmark numbers, methodology, or reproducible latency/throughput figures are included in the evidence pack — only a claim of the benchmark's existence and qualitative community praise. Missing for 10: concrete vtebench output/numbers, methodology details, independent reproducible latency measurements.

   • [github] “Alacritty uses vtebench to quantify terminal emulator throughput and manages to consistently score better than the competition using it.”
   • [community] “It really is the fastest one I ever used. Font rendering is great.”
   • [community] “find /Applications results: Hyper crashed, iTerm2 1:28, Terminal 0:20... Alacritty was surprisingly good, very impressive stuff.”
   • [community] “it also opens faster [than kitty], which is important for me, as I use a tiling window manager and open/close terminals fairly often instead…”

   proof ↗⚑ flag

Rendering

1. developerRely on GPU-accelerated rendering that stays fast and responsive under heavy output

   weight 3 · round to Alacritty
   iTerm2—none0/10

   No evidence in the pack mentions GPU acceleration, rendering architecture, or performance under heavy output/scrollback; the docs and community items cover features like panes, triggers, search, and scripting but nothing about rendering performance or GPU usage.

   ⚑ flag

   Alacritty!disputedcontradicted5/10

   Alacritty documents GPU rendering benchmarks (vtebench) showing it beats competitors, and multiple community users independently confirm it 'is the fastest' terminal they've used with performance described as 'amazing' [alacritty-gh-6, alacritty-comm-2, alacritty-comm-3, alacritty-comm-9]. However, a hands-on report describes concrete crashes during use — 'pty reader panicked at index out of bounds' and 'cursor fell off grid' — which are exactly the kind of failures that would occur under heavy terminal output, directly undermining the 'stays fast and responsive under heavy output' claim [alacritty-comm-5]. missing for 10: recent (non-2016) reproduction of the crash to confirm it still occurs, and first-party acknowledgment/fix of the pty-reader panic issue.

   • [github] “Alacritty uses vtebench to quantify terminal emulator throughput and manages to consistently score better than the competition using it.”
   • [community] “It really is the fastest one I ever used. Font rendering is great.”
   • [community] “find /Applications results: Hyper crashed, iTerm2 1:28, Terminal 0:20... Alacritty was surprisingly good, very impressive stuff.”
   • [community] “I really enjoy Alacritty and use it every day. The performance is amazing!”
   • [community] “Nice, but: thread 'pty reader' panicked at 'index out of bounds'... or thread 'pty reader' panicked at 'cursor fell off grid'.”

   proof ↗⚑ flag

1. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to iTerm2
   iTerm2!disputedcontradicted5/10

   iTerm2's AI feature is documented as an optional, install-only component (iterm2-docs-15), implying users can opt out of any AI-related data sharing by not installing/enabling it. However, hands-on community reports directly contradict this: users found that entering any text (even a stray space) in the OpenAI API key field silently activated data-sending, meaning the feature wasn't truly opt-out/disabled as claimed [iterm2-comm-2], while other users defended the feature as inactive-by-default [iterm2-comm-3]. Missing for 10: no general telemetry/usage-tracking opt-out setting is documented at all (the evidence only covers the AI plugin's data flow to OpenAI, not broader telemetry), and no vendor response addressing the toggle bug is provided.

   • [claimed-docs] “This is an optional component you can install to enable generative AI features in iTerm2.”
   • [community] “"It takes much less effort for me to simply switch back to Terminal.app." (reacting to iTerm2 adding an opt-in OpenAI-based AI feature)”
   • [community] “Users reported that iTerm2's new AI feature wasn't a true disabled toggle: "Put anything in the box for the OpenAI key, valid or not, and th…”
   • [community] “Some users called the backlash overblown: "a feature that is inactive by default, consumes no processing power, memory or anything else" sti…”

   proof ↗⚑ flag

   Alacritty—none0/10

   The evidence pack contains no mention of telemetry, usage tracking, or any opt-out configuration setting for Alacritty; the docs cover config format, keybindings, and installation but never address data collection. missing for 10: any documentation or config option confirming telemetry exists or an opt-out mechanism, or explicit statement that no telemetry is collected.

   ⚑ flag

Graphics

1. developerDisplay inline images and rich graphics via a documented terminal graphics protocol

   weight 2 · round to iTerm2
   iTerm2✓fullcommunity8/10

   iTerm2 documents a custom escape sequence for inline image display (including animated GIFs), and community hands-on evidence corroborates real-world use via imgcat working over SSH. missing for 10: a formal protocol specification page/name (e.g. explicit 'inline images protocol' spec doc) and broader third-party adoption/compatibility discussion beyond one HN thread.

   • [claimed-docs] “iTerm2 has a custom escape sequence to display images right in the terminal. Even animated GIFs!”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”

   proof ↗⚑ flag

   Alacritty—none0/10

   No evidence pack item mentions any inline image protocol (e.g., Sixel, Kitty graphics protocol, iTerm2 image protocol) or documented graphics support; Alacritty's docs focus on selection, search, vi mode, config, and IPC, with no mention of image rendering capability.

   ⚑ flag

Platforms

1. developerRun the same terminal with the same config on macOS, Linux, and Windows

   weight 2 · round to Alacritty
   iTerm2—none0/10

   iTerm2 is a macOS-only application; no evidence pack item claims Linux or Windows support, and a community source explicitly notes the lack of a comparable replacement on Windows or Linux, confirming it does not run cross-platform.

   • [community] “"I'm a little jealous of iTerm, not going to lie. The UX is pretty nice from what I've seen, but I can't find a like for like replacement fo…”
   • [claimed-docs] “iTerm2 is a replacement for Terminal and the successor to iTerm.”

   proof ↗⚑ flag

   Alacritty!disputedcontradicted5/10

   Alacritty documents cross-platform support (Linux, macOS, Windows, BSD) with a single TOML config file that can be imported across platforms (alacritty-gh-1, alacritty-gh-2, alacritty-docs-17, alacritty-docs-8/14), which is the vendor's basis for 'same config everywhere'. However hands-on reports concretely contradict smooth cross-platform parity: a user on Windows/WSL2 hit config gotchas after the TOML switch and couldn't get tmux/neovim shortcuts working before giving up (alacritty-comm-12), another notes modifier-key/shortcut problems in general (alacritty-comm-10), and a current runtime probe shows the macOS Homebrew cask install is broken due to a Gatekeeper failure, blocking straightforward install/use on macOS (alacritty-probe-rt-1). Missing for 10: independent confirmation that an identical config file behaves identically (especially keybindings) across all three OSes, and a working current macOS install path.

   • [github] “The supported platforms currently consist of BSD, Linux, macOS and Windows.”
   • [github] “Alacritty can be installed by using various package managers on Linux, BSD, macOS and Windows.”
   • [claimed-docs] “Alacritty's configuration file uses the TOML format.”
   • [claimed-docs] “Import additional configuration files.”
   • [claimed-docs] “Import additional configuration files. Imports are loaded in order, skipping all missing files, with the importing file being loaded last.”
   • [community] “I gave it a shot on Windows with wsl2. Hit weird config gotchas since they switched to toml, couldn't get tmux/neovim shortcuts to work, gav…”
   • [community] “Alacritty doesn't do well with modifier keys and a lot of keyboard shortcuts don't work in neovim by default. I recommend using foot instead…”
   • [probe] “PROBE runtime (2026-09-04): `brew install --cask alacritty` fails — Homebrew disabled the cask on 2026-09-01 because the published binaries …”

   proof ↗⚑ flag

Ssh

1. developerSSH to remote hosts with the terminal's own integration carrying my terminfo, shell integration, and config along

   weight 2 · round to iTerm2
   iTerm2✓fullcommunity8/10

   iTerm2 documents shell integration explicitly designed to work 'even over ssh', tracking command history, cwd, and hostname (iterm2-docs-8, iterm2-docs-31), plus automatic profile switching keyed to SSH hostname/user (iterm2-docs-10, iterm2-docs-32) and tmux -CC integration that persists sessions across SSH drops (iterm2-docs-12, iterm2-docs-19, iterm2-docs-23). Community hands-on reports corroborate SSH-aware features working in practice, e.g. imgcat rendering images 'even across SSH connections' and it2dl for remote file downloads (iterm2-comm-5, iterm2-comm-6). Missing for 10: explicit documentation of terminfo propagation itself and independent benchmarking of config/profile carry-over reliability across varied SSH setups.

   • [claimed-docs] “iTerm2 may be integrated with the unix shell so that it can keep track of your command history, current working directory, host name, and mo…”
   • [claimed-docs] “iTerm2 can integrate with your shell so it knows where your shell prompt is, what commands you're entering, which host you are on, and what …”
   • [claimed-docs] “you can have iTerm2 switch profiles depending on what you're doing. For example, you can define a profile that's always used when you ssh to…”
   • [claimed-docs] “you can define a profile that's always used when you ssh to some hostname. Or when your username is root. Or even when you're in a particula…”
   • [claimed-docs] “When you run "tmux -CC", a new tmux session is created. An iTerm2 window opens and it acts like a normal iTerm2 window. The difference is th…”
   • [claimed-docs] “When iTerm2 quits or the ssh session is lost, tmux keeps running. You can return to the host you were ssh'ed into and run "tmux -CC attach" …”
   • [claimed-docs] “iTerm2 is integrated with tmux, allowing you to enjoy a native user interface with all the benefits of tmux's persistence.”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”
   • [community] “"Along with imgcat there's it2dl. Downloads a file from the remote system browser-style. It's much more convenient than scp, especially when…”

   proof ↗⚑ flag

   Alacritty—none0/10

   No evidence of any built-in SSH integration feature (e.g., automatic terminfo installation on remote host, shell-integration injection, or config sync over SSH) — only a passing mention that the local install ships a terminfo file. Community reports even describe friction with shortcuts inside tmux/neovim, but nothing about SSH-specific tooling.

   • [claimed-docs] “If you're just interested in the Alacritty binary and you don't need the terminfo file, desktop entry, manual page or shell completions, you…”
   • [community] “Alacritty doesn't do well with modifier keys and a lot of keyboard shortcuts don't work in neovim by default. I recommend using foot instead…”
   • [community] “I gave it a shot on Windows with wsl2. Hit weird config gotchas since they switched to toml, couldn't get tmux/neovim shortcuts to work, gav…”

   proof ↗⚑ flag

Tmux

1. developerUse tmux inside the terminal, or a documented native tmux integration/control mode

   weight 2 · round to iTerm2
   iTerm2✓fullclaimed9/10

   iTerm2 has a well-documented native tmux control mode (tmux -CC) that integrates tmux sessions natively into iTerm2's window/pane UI while preserving persistence across SSH disconnects and app restarts, plus standard tmux-in-terminal usage is naturally supported. Missing for 10: independent hands-on corroboration specifically of tmux -CC mode (community evidence covers other features, not tmux integration directly).

   • [claimed-docs] “When you run "tmux -CC", a new tmux session is created. An iTerm2 window opens and it acts like a normal iTerm2 window. The difference is th…”
   • [claimed-docs] “When iTerm2 quits or the ssh session is lost, tmux keeps running. You can return to the host you were ssh'ed into and run "tmux -CC attach" …”
   • [claimed-docs] “iTerm2 is integrated with tmux, allowing you to enjoy a native user interface with all the benefits of tmux's persistence.”
   • [claimed-docs] “iTerm2's tmux integration solves these problems... A terminal window opens and it acts like a normal iTerm2 window.”

   proof ↗⚑ flag

   Alacritty~partialcommunity5/10

   Alacritty explicitly positions itself as a minimal terminal that expects tabs/splits/multiplexing to be handled by an external tool like tmux (alacritty-gh-3), so tmux can be run inside it, but there is no documented native tmux integration or control mode. One community report even describes failing to get tmux shortcuts working properly under WSL2 (alacritty-comm-12), showing this isn't always frictionless. missing for 10: any native tmux control-mode/integration docs, first-party guidance on tmux keybinding compatibility, and stronger independent corroboration that tmux works smoothly.

   • [github] “This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer)”
   • [community] “I gave it a shot on Windows with wsl2. Hit weird config gotchas since they switched to toml, couldn't get tmux/neovim shortcuts to work, gav…”
   • [community] “it also opens faster [than kitty], which is important for me, as I use a tiling window manager and open/close terminals fairly often instead…”
   • [community] “Alacritty doesn't do well with modifier keys and a lot of keyboard shortcuts don't work in neovim by default. I recommend using foot instead…”

   proof ↗⚑ flag

Agent control

1. ai-native userLet a coding agent programmatically drive the terminal itself — create panes, run commands, read output — through a documented control protocol or API

   weight 3 · round to iTerm2
   iTerm2✓fullcommunity8/10

   iTerm2 ships a documented Python API explicitly for programmatic control — creating/manipulating sessions, panes, tabs, windows, reading and sending text, and building custom automation — plus AppleScript scripting, both well documented and corroborated by independent community praise calling the Python API 'basically AppleScript... but lets you touch pretty much everything.' This directly satisfies an agent programmatically driving panes/commands/output. missing for 10: no explicit example of an AI agent using the API end-to-end, and no independent hands-on report of agent-driven automation specifically (only general scripting use).

   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”

   proof ↗⚑ flag

   Alacritty—none0/10

   Alacritty's only scripting surface is `alacritty msg` IPC, documented solely for creating new windows and reloading config (alacritty-docs-5, alacritty-docs-11/16) — there is no documented protocol for creating panes, running commands, or reading terminal output. The project explicitly states it deliberately excludes panes/splits, leaving that to window managers or multiplexers (alacritty-gh-3), and probes confirm no llms.txt or OpenAPI/API surface exists (alacritty-probe-1, alacritty-probe-2).

   • [claimed-docs] “New windows can be created either by using the `CreateNewWindow` keybinding action, or by executing the `alacritty msg create-window` subcom…”
   • [claimed-docs] “Offer IPC using _alacritty msg_”
   • [claimed-docs] “Offer IPC using alacritty msg”
   • [github] “This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer)”
   • [probe] “PROBE llms.txt: HTTP 404 at https://alacritty.org/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://alacritty.org/openapi.json, https://alacritty.org/swagger.json, https://alacritty.org/api/op…”

   proof ↗⚑ flag

Extensibility

1. developerExtend the terminal with scripts or plugins in a real language (Lua, Python, kittens) beyond built-in options

   weight 2 · round to iTerm2
   iTerm2✓fullcommunity8/10

   iTerm2 offers a documented Python API for full automation/customization (custom status bar components, triggers, menu items, new features), plus AppleScript scripting and trigger-invoked Python scripts, with community hands-on praise calling it 'basically AppleScript... but not soul-crushing to write' and noting real-world tools like imgcat/it2dl built on it. This covers 'real language' scripting well beyond built-in options, though there's no mention of Lua or 'kittens' (a kitty-terminal concept) support specifically. Missing for 10: Lua scripting support, kitten-style plugin format, independent third-party plugin ecosystem showcase.

   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”
   • [github] “Triggers - Regex patterns that fire actions when matched: highlight text, run commands, send notifications, open password manager, set marks…”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”

   proof ↗⚑ flag

   Alacritty—none0/10

   Alacritty's documented feature set is limited to TOML config, IPC via `alacritty msg`, vi-mode, search, and hints — there is no mention of Lua/Python scripting or a kittens-style plugin system, and the project explicitly positions itself as minimal (leaving multiplexing/extra features to other tools).

   • [claimed-docs] “Import additional configuration files.”
   • [claimed-docs] “Offer IPC using _alacritty msg_”
   • [claimed-docs] “Alacritty's configuration file uses the TOML format.”
   • [github] “This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer)”
   • [github] “The software is considered to be at a **beta** level of readiness; there are a few missing features and bugs to be fixed, but it is already …”

   proof ↗⚑ flag

Layouts

1. power-userDefine startup sessions and window layouts in config or scripts so a project workspace opens in one command

   weight 2 · round to iTerm2
   iTerm2✓fullcommunity8/10

   iTerm2's AppleScript scripting explicitly supports launching the app and opening multiple sessions with profiles into new tabs/windows (a scripted workspace startup), and the Python API/triggers offer additional automation of session/window setup; profiles themselves can also be tied to directories/hosts for one-command workspace opening. missing for 10: no first-party example of a saved 'window arrangement' config file format or direct hands-on community confirmation of a single-command full-layout launch.

   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [claimed-docs] “you can define a profile that's always used when you ssh to some hostname. Or when your username is root. Or even when you're in a particula…”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”

   proof ↗⚑ flag

   Alacritty—none0/10

   Alacritty explicitly excludes window/session management, deferring tabs, splits, and layouts to external window managers or terminal multiplexers rather than providing built-in session/workspace config; no evidence of a startup-session or layout scripting mechanism exists in the pack.

   • [github] “This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer)”
   • [community] “I really disagree with the author's definition of minimal. I need scrollback, tabs, and monitor for activity/silence - I can't really use th…”
   • [community] “I used to use kitty, but its CPU usage was on the higher side. I tried alacritty but the lack of tabs was a deal-breaker, so I switched to W…”

   proof ↗⚑ flag

Remote control

1. developerScript and control the terminal from the command line — open windows, send text, query state — via a documented CLI or IPC interface

   weight 3 · round to iTerm2
   iTerm2✓fullcommunity8/10

   iTerm2 documents a robust Python API for scripting/controlling the terminal (open sessions, send text, query state) and AppleScript support for launching/controlling sessions, with independent community corroboration praising the Python API's power over AppleScript. missing for 10: no evidence of a CLI-only (non-Python/AppleScript) IPC socket documentation, and no hands-on demonstration of specific 'query state' calls beyond general docs.

   • [claimed-docs] “iTerm2 offers a Python package which makes it easy to write Python scripts that control iTerm2 and extend its behavior.”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [claimed-docs] “iTerm2 has sophisticated AppleScript support allowing one to write stand-alone scripts to launch the application and open multiple sessions …”
   • [github] “Python Scripting API - Full automation and customization via Python. Create custom status bar components, triggers, menu items, or entirely …”
   • [community] “"imgcat: you can view images without leaving your terminal. Somehow this works even across SSH connections… Python scripting API: basically …”

   proof ↗⚑ flag

   Alacritty~partialprobed5/10

   Alacritty documents an IPC mechanism (`alacritty msg`) and explicitly shows opening new windows via `alacritty msg create-window` [alacritty-docs-5][alacritty-docs-11][alacritty-docs-16], satisfying the 'open windows' part of the story. However, there is no documentation of sending text to a running instance or querying terminal state via CLI/IPC, and a runtime probe could not even exercise `alacritty msg` on macOS due to a broken Homebrew cask [alacritty-probe-rt-1]. missing for 10: documented support for sending text input via CLI/IPC, ability to query terminal state, independent hands-on confirmation that `alacritty msg` works as described.

   • [claimed-docs] “New windows can be created either by using the `CreateNewWindow` keybinding action, or by executing the `alacritty msg create-window` subcom…”
   • [claimed-docs] “Offer IPC using _alacritty msg_”
   • [claimed-docs] “Offer IPC using alacritty msg”
   • [probe] “PROBE runtime (2026-09-04): `brew install --cask alacritty` fails — Homebrew disabled the cask on 2026-09-01 because the published binaries …”

   proof ↗⚑ flag

Command tracking

1. developerI get command-aware features from shell integration, like exit status, duration, and notifications when long commands finish

   weight 2 · round to iTerm2
   iTerm2✓fullclaimed8/10

   iTerm2's shell integration docs confirm tracking of command history, prompts, directories, and hostnames, plus notifications for job completion/bells/activity and prompt navigation shortcuts. missing for 10: explicit documentation citing per-command exit status/duration display and independent hands-on confirmation of the notification-on-completion behavior.

   • [claimed-docs] “iTerm2 may be integrated with the unix shell so that it can keep track of your command history, current working directory, host name, and mo…”
   • [claimed-docs] “iTerm2 can integrate with your shell so it knows where your shell prompt is, what commands you're entering, which host you are on, and what …”
   • [claimed-docs] “You can choose to receive notifications of activity, bells, job completion, and more.”
   • [claimed-docs] “you can easily navigate to previous shell prompts with ⇧⌘↑ and ⇧⌘↓”
   • [claimed-docs] “you can enable shell integration by enabling **Load shell integration automatically** in **Settings > Profiles > General**”

   proof ↗⚑ flag

   Alacritty—none0/10

   No evidence of any shell-integration features like exit status reporting, command duration tracking, or completion notifications; Alacritty's documented feature set covers vi mode, search, selection, IPC/config, but nothing about command-aware shell integration.

   ⚑ flag

Marks

1. developerJump between prompts and command marks in my scrollback thanks to shell integration

   weight 2 · round to iTerm2
   iTerm2✓fullclaimed9/10

   iTerm2's shell integration explicitly tracks prompts and sets marks at each command, and docs describe navigating between previous shell prompts with ⇧⌘↑/⇧⌘↓, corroborated by GitHub feature list mentioning marks at each prompt and copy mode working with marks to jump between prompts. Missing for 10: no independent hands-on account specifically confirming the prompt-jump keybinding in practice beyond docs/GitHub summaries.

   • [claimed-docs] “iTerm2 may be integrated with the unix shell so that it can keep track of your command history, current working directory, host name, and mo…”
   • [claimed-docs] “you can easily navigate to previous shell prompts with ⇧⌘↑ and ⇧⌘↓”
   • [claimed-docs] “iTerm2 can integrate with your shell so it knows where your shell prompt is, what commands you're entering, which host you are on, and what …”
   • [claimed-docs] “you can enable shell integration by enabling **Load shell integration automatically** in **Settings > Profiles > General**”
   • [github] “Enables click-to-download files via SCP, drag-and-drop uploads, command history per host, recent directories by "frecency," and marks at eac…”
   • [github] “Vim-like keyboard selection. Navigate and select text without touching the mouse. Works with marks to jump between command prompts.”

   proof ↗⚑ flag

   Alacritty—none0/10

   The evidence covers vi-mode navigation, scrollback search, and text selection, but there is no mention of shell integration (e.g., OSC 133 prompt/command marks) or a jump-to-previous/next-prompt feature. Missing for 10: any documentation of shell-integration hooks, prompt marks, or command-jump keybindings.

   • [claimed-docs] “The vi mode allows moving around Alacritty's viewport and scrollback using the keyboard.”
   • [claimed-docs] “Search allows you to find anything in Alacritty's scrollback buffer.”
   • [claimed-docs] “In vi mode the search is bound to / for forward and ? for backward search.”

   proof ↗⚑ flag

Discoverability

1. power-userDiscover and run terminal actions from a searchable command palette

   weight 1 · round to iTerm2
   iTerm2~partialclaimed4/10

   iTerm2's 'Open Quickly' (Cmd-Shift-O) is a searchable palette, but evidence describes it only as a search across sessions by tab title, command, hostname, directory, or badge — not a general command palette for discovering and invoking arbitrary terminal actions/menu commands. Missing for 10: evidence of listing/searching actual app commands or actions (not just sessions), evidence of executing arbitrary actions from the palette, and independent confirmation of this behaving like a true command palette.

   • [github] “Open Quickly - Cmd-Shift-O opens a search across all sessions by tab title, command, hostname, directory, or badge. Navigate large session c…”
   • [github] “Cmd-Shift-O opens a search across all sessions by tab title, command, hostname, directory, or badge. Navigate large session collections inst…”
   • [github] “Open Quickly - Cmd-Shift-O opens a search across all sessions by tab title, command, hostname, directory, or badge.”
   • [claimed-docs] “Just type the start of any word that has ever appeared in your window and then Cmd-; will pop open a window with suggestions.”

   proof ↗⚑ flag

   Alacritty—none0/10

   Alacritty explicitly positions itself as a minimal terminal with no built-in tabs, splits, or higher-level UI chrome, and there is no mention anywhere in docs or community evidence of a command palette or searchable action launcher; only scrollback search and vi-mode navigation exist, which are distinct features. No evidence supports discoverable/searchable command execution.

   • [github] “This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer)”
   • [claimed-docs] “Search allows you to find anything in Alacritty's scrollback buffer.”
   • [claimed-docs] “Terminal hints allow easily interacting with visible text without having to start vi mode.”

   proof ↗⚑ flag

Hyperlinks

1. developerOpen URLs and file paths from output by clicking them or selecting them from the keyboard

   weight 2 · round to iTerm2
   iTerm2✓fullcommunity9/10

   Smart Selection with quad-click and Cmd-click to open URLs/paths, plus keyboard-based selection (Copy Mode/vim-like navigation), are documented and corroborated by community hands-on reports (Semantic History opening files in editor via Cmd+Click). missing for 10: no independent verification of full keyboard-only 'select and open' flow beyond selection, only Cmd-click for opening.

   • [github] “Smart Selection - Quad-click selects semantic objects (URLs, file paths, email addresses, quoted strings). Right-click for context actions. …”
   • [claimed-docs] “iTerm2 can perform "smart selection" to highlight URLs, email addresses, filenames, and more by recognizing what is under the cursor”
   • [claimed-docs] “iTerm2 can perform "smart selection" to highlight URLs, email addresses, filenames, and more by recognizing what is under the cursor.”
   • [github] “Vim-like keyboard selection. Navigate and select text without touching the mouse. Works with marks to jump between command prompts.”
   • [github] “Copy Mode - Vim-like keyboard selection. Navigate and select text without touching the mouse.”
   • [community] “"Semantic History is pretty handy and not well-known. It lets you Command+Click on a path to open it in your editor (or associated applicati…”
   • [claimed-docs] “Use the keyboard to make and modify selections.”

   proof ↗⚑ flag

   Alacritty~partialclaimed6/10

   Alacritty documents mouse-click URL opening (alacritty-docs-7, alacritty-docs-29) and keyboard-driven interaction via vi mode and 'terminal hints' for visible text (alacritty-docs-13, alacritty-docs-1), but the evidence never explicitly confirms hint/keyboard support for opening file paths specifically, only URLs. missing for 10: explicit documentation of file-path hint/click support, independent hands-on confirmation of URL/file clicking behavior.

   • [claimed-docs] “You can open URLs with your mouse by clicking on them.”
   • [claimed-docs] “You can open URLs with your mouse by clicking on them. The modifiers required to be held and program which should open the URL can be setup …”
   • [claimed-docs] “Terminal hints allow easily interacting with visible text without having to start vi mode.”
   • [claimed-docs] “The vi mode allows moving around Alacritty's viewport and scrollback using the keyboard.”

   proof ↗⚑ flag

Scrollback

1. developerSearch my scrollback quickly and jump between matches

   weight 2 · round drawn
   iTerm2✓fullclaimed8/10

   Docs describe a robust find-on-page feature with instant highlighting of all matches and regex support, plus Global Search across all tabs, directly matching the story of searching scrollback and jumping between matches. Missing for 10: independent hands-on confirmation of match-jump behavior (next/prev match navigation) and details on keyboard shortcuts for cycling matches.

   • [claimed-docs] “iTerm2 comes with a robust find-on-page feature. The UI stays out of the way. All matches are immediately highlighted. Even regular expressi…”
   • [claimed-docs] “iTerm2 comes with a robust find-on-page feature... Even regular expression support is offered!”
   • [claimed-docs] “Search all your tabs at once with Global Search.”

   proof ↗⚑ flag

   Alacritty✓fullclaimed8/10

   Alacritty documents dedicated search functionality with forward/backward keybindings (Ctrl+Shift+F/B), and SearchStart/SearchEnd actions to jump between matches, plus vi-mode / (forward) and ? (backward) search integration. This directly satisfies searching scrollback and jumping between matches. Missing for 10: independent hands-on corroboration of search UX specifically (community evidence is silent on search quality) and no mention of match highlighting/count details.

   • [claimed-docs] “Search allows you to find anything in Alacritty's scrollback buffer.”
   • [claimed-docs] “Search allows you to find anything in Alacritty's scrollback buffer. You can search forward using Ctrl Shift f (Command f on macOS) and back…”
   • [claimed-docs] “The `SearchStart` and `SearchEnd` keybinding actions can be bound if you're looking for a way to jump to the start or the end of a match.”
   • [claimed-docs] “In vi mode the search is bound to / for forward and ? for backward search.”

   proof ↗⚑ flag