Warp vs Alacritty

Agent access

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

   weight 2 · round to Warp
   Warp✓fullprobed9/10

   Warp publishes a dedicated llms.txt (confirmed live via HTTP 200 probe at docs.warp.dev/llms.txt) describing its agentic docs, plus a whole family of agent-oriented doc pages under the _llms-txt/ path (code, warp-agent-cli, automation-platform, api-reference, knowledge-and-collaboration, factories), giving AI agents a structured, machine-readable entry point into Warp's documentation. Missing for 10: no independent/community confirmation that an external agent has actually consumed this llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.warp.dev/llms.txt # Warp > Documentation for Warp, the agentic development environment. Covers the…”
   • [claimed-docs] “Warp comes with a native code editor designed for quick, in-flow edits alongside your Agent conversations... with essentials like syntax hig…”
   • [claimed-docs] “Because it’s a regular command-line program, it works in any terminal emulator, including over SSH.”
   • [claimed-docs] “Cloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, o…”
   • [claimed-docs] “open the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review.”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”
   • [claimed-docs] “The Admin Panel gives team administrators centralized control over organization-wide Warp settings, including agent autonomy, privacy contro…”
   • [claimed-docs] “A software factory takes in requests (bug reports, feature specs, support escalations), and a coordinated fleet of agents works them into a …”

   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 to Warp
   Warp✓fullclaimed8/10

   Warp ships the Oz CLI explicitly documented for running/managing cloud agents 'from any terminal, script, or CI pipeline,' with API keys for headless/non-interactive auth 'ideal for CI pipelines, headless servers, and containers,' plus the standalone Warp Agent CLI that works over SSH/any terminal without the desktop app. Schedules and webhook/event triggers further support automation use cases outside interactive sessions. Missing for 10: independent/hands-on verification of actual CI pipeline runs and more detail on exit codes/output parsing for scripting.

   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline. Use it to start …”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”
   • [claimed-docs] “Because it’s a regular command-line program, it works in any terminal emulator, including over SSH.”
   • [claimed-docs] “The Warp Agent CLI lets you switch directories while in an agent session, and even run agents on remote machines without installing remote b…”
   • [claimed-docs] “Triggers: React to events from Slack, Linear, GitHub, or custom webhooks”
   • [claimed-docs] “Schedules: Run recurring tasks like dependency updates or dead code removal”
   • [claimed-docs] “Cloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, o…”

   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 userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Warp
   Warp✓fullclaimed9/10

   Warp has documented, first-party support for connecting MCP servers to extend its agents ('MCP servers extend Warp's local agents... acting as plugins for Warp'), plus explicit CLI support (Oz CLI) to 'connect MCP servers like GitHub and Linear' and agent profiles to control MCP server usage. This is corroborated across multiple doc pages describing MCP as a first-class integration point for tool use. Missing for 10: independent/hands-on community confirmation of MCP server usage specifically (community evidence covers other topics, not MCP directly).

   • [claimed-docs] “Connect Warp AI to any tool via the Model Context Protocol. Pull context from databases, APIs, docs, and internal services so the AI underst…”
   • [claimed-docs] “MCP servers extend Warp’s local agents in a modular, flexible way by exposing custom tools or data sources through a standardized interface …”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline. Use it to start …”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”
   • [claimed-docs] “Agent Profiles - Use agent profiles to control what the agent can access, how it behaves, and where it can act, including file access, comma…”

   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

4. ai-native userUse an official CLI

   weight 2 · round to Warp
   Warp✓fullclaimed8/10

   Warp ships multiple official CLIs — the standalone Warp Agent CLI usable in any terminal/SSH (warp-docs-23, warp-docs-41, warp-docs-59, warp-docs-69) and the Oz CLI for managing cloud agents in scripts/CI (warp-docs-22, warp-docs-37, warp-docs-52) — both extensively documented as first-party, agent-native tooling with API key auth for headless use (warp-docs-63). Missing for 10: independent/hands-on community corroboration specifically validating the CLI's real-world reliability (community evidence covers the desktop app, not the CLI).

   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.”
   • [claimed-docs] “The Warp Agent CLI lets you switch directories while in an agent session, and even run agents on remote machines without installing remote b…”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline. Use it to start …”
   • [claimed-docs] “The Warp Agent is now available as a standalone CLI that you can use anywhere – Ghostty, iTerm 2, VS Code, built-in Windows and Mac Terminal…”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”
   • [claimed-docs] “Because it’s a regular command-line program, it works in any terminal emulator, including over SSH.”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”
   • [claimed-docs] “It creates and maintains its own pseudoterminal (PTY), which lets you and the agent execute commands and interact with running processes thr…”

   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

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

   weight 3 · round to Warp
   Warp✓fullprobed8/10

   Warp explicitly advertises an 'API, CLI, SDK and MCP' platform (warp-docs-42), and a live probe confirms a real OpenAPI spec is served at docs.warp.dev/openapi.json (warp-probe-2), backed by a documented CLI reference (warp-probe-3) and API-key based headless auth for the Oz CLI (warp-docs-63) plus scriptable agent control (warp-docs-22, warp-docs-37, warp-docs-52). Missing for 10: independent/third-party corroboration of API usage and more detailed public API reference content beyond the openapi.json existence check.

   • [claimed-docs] “API, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key”
   • [probe] “official CLI documented at https://docs.warp.dev/reference/cli”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline. Use it to start …”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”

   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

6. ai-native userSubscribe to events via webhooks

   weight 2 · round to Warp
   Warp~partialclaimed4/10

   Warp's automation platform docs mention 'Triggers: React to events from Slack, Linear, GitHub, or custom webhooks' and cloud agents 'triggered by... integrations like Slack and GitHub,' indicating webhook-based triggering exists, but this describes Warp consuming/reacting to inbound webhooks to kick off agents rather than a documented outbound webhook subscription mechanism for external systems to receive Warp's own events. Missing for 10: explicit documentation of an outbound webhook/event-subscription API, payload schema, or delivery guarantees, and independent confirmation of this feature working.

   • [claimed-docs] “Triggers: React to events from Slack, Linear, GitHub, or custom webhooks”
   • [claimed-docs] “Cloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, o…”

   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

Agentic features

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

   weight 2 · round to Warp
   Warp✓fullclaimed8/10

   Warp's Automation Platform explicitly supports cloud agents that run autonomously in the background, triggered by schedules, webhooks, or integrations like Slack/GitHub/Linear (warp-docs-4, warp-docs-5, warp-docs-60), with observability/audit trails (warp-docs-53, warp-docs-61) and CLI/API control via Oz CLI for headless/CI use (warp-docs-22, warp-docs-37, warp-docs-63). missing for 10: independent/hands-on verification of autonomous background runs actually completing unattended, and more detail on failure handling/reliability at scale.

   • [claimed-docs] “Triggers: React to events from Slack, Linear, GitHub, or custom webhooks”
   • [claimed-docs] “Schedules: Run recurring tasks like dependency updates or dead code removal”
   • [claimed-docs] “Cloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, o…”
   • [claimed-docs] “open the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review.”
   • [claimed-docs] “Observability: Every run is tracked, auditable, and shareable with your team”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline. Use it to start …”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”

   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 to Warp
   Warp✓fullprobed8/10

   A probe directly confirms an OpenAPI JSON spec is served at docs.warp.dev/openapi.json returning a valid 'openapi' key, and docs reference an API/CLI/SDK/MCP platform with API key management, corroborating a machine-readable spec exists. Missing for 10: no independent/third-party confirmation of spec completeness or versioning, and no docs page walking through consuming the spec.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key”
   • [claimed-docs] “API, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”

   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 Warp
   Warp✓fullcommunity9/10

   Warp's built-in Agent Mode is extensively documented to plan and execute multi-step terminal tasks (writing code, running commands, controlling interactive/full-screen apps, iterating) while keeping the user in the loop via conversation view, follow-ups, and approval/steering ('watch, steer, and hand off runs'). This is corroborated across many first-party docs and independent community mentions of using it as a daily driver for AI-assisted terminal work, though some hands-on complaints exist about unrelated reliability/telemetry issues rather than the core delegate-and-approve workflow itself. Missing for 10: independent hands-on verification specifically of the approval/plan-then-execute step (vs. general agent usage), and confirmation the community complaints don't touch this exact workflow.

   • [claimed-docs] “Describe what you want to build and let Warp's built‑in agent handle the rest — writing code, running commands, and iterating until the task…”
   • [claimed-docs] “Write and refactor code across your codebase * Debug issues and fix errors * Run commands and interpret results * Plan and execute mul…”
   • [claimed-docs] “the Warp Agent can now run and control long-running or full-screen terminal applications. The agent can provide input when prompted, navigat…”
   • [claimed-docs] “By default, if you ask an AI query immediately after interacting in Agent Mode, your query is sent as a **follow-up** to the current convers…”
   • [claimed-docs] “Conversations are tied to sessions and you can run multiple Agent Mode conversations simultaneously in different windows, tabs, or panes.”
   • [claimed-docs] “any surface — watch, steer, and hand off runs from web, mobile, terminal, or IDE.”
   • [community] “Warp is great - I use it as my daily terminal. The best features are being able to edit commands, chunking the output into blocks and AI gen…”
   • [community] “My daily driver for a few months now, even after trying Rio/Ghostty/Wezterm... Favorite feature is the notification when a long running comm…”

   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 Warp
   Warp!disputedcontradicted4/10

   Warp docs promise granular control (secret redaction, no training use, telemetry opt-out on paid plans, ZDR for Business/Enterprise) and note telemetry can be monitored/disabled, but this is undercut by concrete community reports: one HN thread describes Warp silently sending terminal session data to LLMs via 'Prompt Suggestions'/'Next Command' without explicit consent (warp-comm-1), and multiple independent users report being confronted with a mandatory login prompt and uninstalling immediately (warp-comm-5, warp-comm-6, warp-comm-16), even though a Warp co-founder claims the login requirement was removed (warp-comm-7). Docs also admit telemetry must stay on to use AI on the Free plan (warp-docs-33), meaning full AI use without any data leaving isn't unconditional. missing for 10: a documented explicit toggle to fully disable AI without any account/login step on the free tier, and resolution of the community claim of undisclosed data transmission.

   • [claimed-docs] “Warp does not allow OpenAI or Anthropic to use your data for model training. Our "hands off" approach also means your terminal input and out…”
   • [claimed-docs] “Monitor telemetry in real-time with Warp’s native Network Log. Opt out of telemetry at any time”
   • [claimed-docs] “Telemetry must be enabled to use AI features on the Free plan, while paid plans can opt out at any time and continue using Warp, including A…”
   • [claimed-docs] “Business and Enterprise plans are covered by our Zero Data Retention (ZDR) agreement. No AI interaction or console data is ever collected.”
   • [claimed-docs] “Read a complete list of all the telemetry events that get sent for app analytics ... Opt out of telemetry at any time”
   • [claimed-docs] “Warp unconditionally applies Secret Redaction in all AI interactions to ensure that any sensitive data is _never_ collected or sent to third…”
   • [community] “Warp silently sends terminal session data to LLMs via 'Prompt Suggestions' and 'Next Command' features without explicit consent, discovered …”
   • [community] “I tried Warp once... it showed me a login prompt. Perhaps I mistakenly downloaded a login prompt app instead of a terminal app? I promptly u…”
   • [community] “I remember seeing this terminal emulator, deciding to give it a shot, and being asked to sign in. I have never uninstalled a program faster …”
   • [community] “Warp co-founder: fair criticism, and this is the reason we removed the login requirement... the point of the login is that we have features …”
   • [community] “They have also innovated by requiring login (into a console!!)... Today they have heaps of telemetry, so a privacy nightmare. This is a term…”

   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 Warp
   Warp✓fullclaimed8/10

   Warp's Automation Platform explicitly supports Triggers reacting to events from Slack, Linear, GitHub, or custom webhooks, plus Schedules for recurring tasks, and cloud agents described as 'triggered by system events, schedules, or integrations like Slack and GitHub' with full observability/audit trails. This directly matches the story of defining rules that trigger automatic actions on events. Missing for 10: independent/hands-on verification of the trigger system in practice (community evidence focuses on core terminal/agent issues, not the automation/trigger feature specifically).

   • [claimed-docs] “Triggers: React to events from Slack, Linear, GitHub, or custom webhooks”
   • [claimed-docs] “Schedules: Run recurring tasks like dependency updates or dead code removal”
   • [claimed-docs] “Cloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, o…”
   • [claimed-docs] “open the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review.”
   • [claimed-docs] “Observability: Every run is tracked, auditable, and shareable with your team”

   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 to Warp
   Warp✓fullclaimed8/10

   Warp documents explicit 'Schedules' functionality for cloud agents ('Run recurring tasks like dependency updates or dead code removal') alongside 'Triggers' for event-based automation, plus cloud agents described as 'triggered by system events, schedules, or integrations' and managed via the Oz CLI for scripting/CI. This directly matches the story of scheduling recurring jobs/workflows. Missing for 10: independent/hands-on confirmation of the scheduling feature working reliably, and more detail on scheduling configuration (cron-like syntax, frequency options).

   • [claimed-docs] “Triggers: React to events from Slack, Linear, GitHub, or custom webhooks”
   • [claimed-docs] “Schedules: Run recurring tasks like dependency updates or dead code removal”
   • [claimed-docs] “Cloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, o…”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”

   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 userVersion, review, and roll back my automations

   weight 1 · round to Warp
   Warp~partialclaimed4/10

   Warp provides strong review/observability for automations (run transcripts showing prompt, plan, commands, logs, shareable for team review) and lets you save/share workflows via Warp Drive, but there is no documented versioning or rollback mechanism for automations (e.g., no version history, diffing, or revert capability for schedules/triggers/workflows). missing for 10: explicit version history for saved automations, ability to roll back to a prior automation version, changelog/diff view for automation edits.

   • [claimed-docs] “Warp lets you save your most important workflows in Warp Drive so you can run them on‑demand or share with your team.”
   • [claimed-docs] “Observability: Every run is tracked, auditable, and shareable with your team”
   • [claimed-docs] “open the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review.”
   • [claimed-docs] “Warp lets you save your most important workflows in Warp Drive so you can run them on‑demand or share with your team. Let Warp AI handle the…”
   • [claimed-docs] “Cloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, o…”

   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

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
   Warp~partialclaimed4/10

   Warp's open-source announcement mentions shipping a new settings file explicitly for 'programmatic control over settings and easy portability between devices' (warp-docs-40), which speaks directly to the dotfiles/sync use case, but this is a single passing mention with no documentation of its format, scope, or actual dotfiles-style workflow. Other config-adjacent features (theme OS-sync, session restoration) are separate app-state features, not plain-text portable config. Missing for 10: dedicated docs on the settings file format/location, confirmation it covers full app config (keybindings, workflows, themes), and independent/community corroboration of dotfiles-style syncing across machines.

   • [claimed-docs] “we are shipping a (long-overdue) settings file so that users and agents get programmatic control over settings and easy portability between …”
   • [claimed-docs] “Warp supports synchronizing your theme with the OS’s light and dark themes.”
   • [claimed-docs] “Restore your windows, tabs, panes, and recent Blocks automatically when you relaunch Warp.”

   proof ↗⚑ 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
   Warp—none0/10

   No evidence in the pack mentions font configuration, ligatures, fallback fonts, or font tuning of any kind; documentation focuses on themes, appearance sync, and agent features, not typography settings.

   ⚑ 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 Warp
   Warp✓fullclaimed8/10

   Warp's docs explicitly support custom themes, auto-generating themes from a background image, and syncing theme with OS light/dark mode (warp-docs-19, warp-docs-20), directly matching the story. Missing for 10: independent/community corroboration of theming reliability and more detail on breadth of built-in theme palette.

   • [claimed-docs] “Automatically create new themes based on a background image.”
   • [claimed-docs] “Warp supports synchronizing your theme with the OS’s light and dark themes.”

   proof ↗⚑ 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 Warp
   Warp~partialprobed6/10

   Warp explicitly positions itself as 'API, CLI, SDK and MCP built as a platform,' with the Oz CLI enabling agent creation, monitoring, MCP connections, and authentication without the desktop app, and a live OpenAPI spec — showing substantial API/CLI parity for agent workflows. But the story demands full UI-equivalent capability, and evidence doesn't confirm parity for many UI-only features (theming, session restoration, conversation UI, code editor) nor is there independent verification that the API surface is fully complete. missing for 10: independent confirmation of full feature parity, evidence that UI-specific features (themes, editor, session restore) are also API-accessible

   • [claimed-docs] “API, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.”
   • [claimed-docs] “any surface — watch, steer, and hand off runs from web, mobile, terminal, or IDE.”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline. Use it to start …”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”
   • [claimed-docs] “Agent Profiles - Use agent profiles to control what the agent can access, how it behaves, and where it can act, including file access, comma…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key”
   • [probe] “official CLI documented at https://docs.warp.dev/reference/cli”

   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 to Warp
   Warp~partialclaimed3/10

   Warp documents a settings file for 'programmatic control over settings and easy portability between devices' and open-sources its client code, but there's no documented feature for exporting conversation history, Warp Drive workflows, or agent run data in open formats for full user data portability. missing for 10: explicit full data export tooling, open-format export of conversation/session history, Warp Drive workflow export, independent confirmation users can fully migrate away with their data.

   • [claimed-docs] “we are shipping a (long-overdue) settings file so that users and agents get programmatic control over settings and easy portability between …”
   • [claimed-docs] “Read and audit Warp’s client source code at warpdotdev/warp, open source under AGPL v3”
   • [claimed-docs] “Warp’s source code is now available at github.com/warpdotdev/warp with an AGPL license.”

   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
   Warp✓fullclaimed8/10

   Warp explicitly published its client source code on GitHub under the AGPL v3 open-source license, documented in both its privacy docs and a dedicated blog post announcing the move to open source. missing for 10: independent/third-party confirmation of the full scope of open-sourced code (e.g., whether cloud/server-side agent components are also included) and any hands-on community audit of the repository beyond the vendor's own announcement.

   • [claimed-docs] “Read and audit Warp’s client source code at warpdotdev/warp, open source under AGPL v3”
   • [claimed-docs] “Warp’s source code is now available at github.com/warpdotdev/warp with an AGPL license.”
   • [claimed-docs] “Read and audit Warp’s client source code at `warpdotdev/warp`, open source under AGPL v3”

   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 to Warp
   Warp~partialcommunity4/10

   Warp's client is open-sourced under AGPL v3 (warpdotdev/warp) so the terminal client itself can be inspected and self-hosted/built from source, and cloud agents are described as able to run 'on Warp's cloud infrastructure or your own,' suggesting some self-hosting of agent execution. However, there's no documented path to self-host the full core product—AI model routing, backend services, and account/login (required per warp-comm-6/7) remain tied to Warp's proprietary cloud, and no deployment/on-prem guide is evidenced. Missing for 10: a documented self-hosted backend/server deployment, evidence that AI/model-routing works without Warp's cloud, and independent confirmation of a working self-hosted setup.

   • [claimed-docs] “Read and audit Warp’s client source code at warpdotdev/warp, open source under AGPL v3”
   • [claimed-docs] “Warp’s source code is now available at github.com/warpdotdev/warp with an AGPL license.”
   • [claimed-docs] “Cloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, o…”
   • [community] “Warp co-founder: fair criticism, and this is the reason we removed the login requirement... the point of the login is that we have features …”

   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

Multiplexing

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

   weight 3 · round to Warp
   Warp~partialclaimed6/10

   Docs confirm panes exist alongside tabs and windows as first-class session units (agent conversations run in "windows, tabs, or panes" and session restoration recreates "windows, tabs, and panes"), showing built-in multiplexing without needing tmux. However the pack lacks any detail on pane-splitting mechanics, keyboard shortcuts, or layout management, and no independent/hands-on account discusses pane usage specifically. Missing for 10: dedicated documentation on split/pane creation and navigation, independent user confirmation of pane workflow.

   • [claimed-docs] “Conversations are tied to sessions and you can run multiple Agent Mode conversations simultaneously in different windows, tabs, or panes.”
   • [claimed-docs] “Restore your windows, tabs, panes, and recent Blocks automatically when you relaunch Warp.”
   • [claimed-docs] “Continue previous threads with follow-ups, manage conversation history, attach context from blocks and files, and run multiple conversations…”

   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 drawn
   Warp—none0/10

   No evidence in the pack mentions a global hotkey or quake-style dropdown/instant-summon window feature; Warp's docs focus on session restoration, panes/tabs, and AI agent features, not a system-wide invocation shortcut.

   ⚑ 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 Warp
   Warp✓fullclaimed8/10

   Warp's docs explicitly describe session restoration that restores windows, tabs, panes, and recent Blocks automatically on relaunch, directly matching the story. Missing for 10: independent/hands-on corroboration of restore reliability after crashes (only vendor docs cited), and no detail on working-directory restoration specifics.

   • [claimed-docs] “Restore your windows, tabs, panes, and recent Blocks automatically when you relaunch Warp.”
   • [claimed-docs] “Session restoration allows you to quickly pick up where you left off in your previous terminal session.”
   • [claimed-docs] “Sometimes, you may want to prevent a sensitive Block from being saved on your computer, or you may want to clear blocks from a machine entir…”

   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
   Warp—none0/10

   No published benchmarks, latency, or throughput figures appear anywhere in the evidence pack; documentation focuses on features and privacy, while community posts mention performance complaints but no measured numbers. missing for 10: published benchmark data, latency/throughput measurements, any comparative performance testing.

   ⚑ 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
   Warp—none0/10

   The evidence pack contains no first-party documentation claiming GPU-accelerated rendering or describing rendering performance under heavy output; instead, community reports describe UI glitches, broken behavior, and instability during heavy use (e.g., 'horribly broken... UI glitches', 'random failures, stopping of agents'), and one commenter notes the terminal is 'just Alacritty' with no Warp-specific performance claims. Since no vendor documentation asserts this capability, there's nothing concrete to substantiate 'full' or 'partial', and the negative community signals reinforce a 'none' verdict rather than a dispute of an explicit claim.

   • [community] “Warp is so horribly broken right now and has been for weeks. Multiple github issues on consistent issue writing file. On top of that UI glit…”
   • [community] “I've been a Pro user for several months (use < 1000 credits a month) - but I've noticed a real reduction in quality over the past month or s…”
   • [community] “Warp is a terrible product, and I have nothing nice to say about them. But look at modern terminals like Kitty or Ghostty... mouse support t…”
   • [community] “Their terminal is just Alacritty... The terminal emulator was never their selling point, the AI wrapper was.”

   proof ↗⚑ 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 Warp
   Warp~partialcommunity7/10

   Warp's docs explicitly describe a telemetry opt-out and a Network Log to monitor telemetry in real time, and state paid plans can opt out at any time while still using AI. However, the Free plan requires telemetry to be enabled to use AI features, meaning opt-out isn't universal, and community commentary (warp-comm-1, warp-comm-16) raises concerns about undisclosed data sharing and 'heaps of telemetry,' which tempers full confidence though it doesn't concretely disprove the opt-out mechanism itself. missing for 10: independent verification that opt-out fully works with no residual telemetry, and free-tier parity for full opt-out.

   • [claimed-docs] “Monitor telemetry in real-time with Warp’s native Network Log. Opt out of telemetry at any time”
   • [claimed-docs] “Telemetry must be enabled to use AI features on the Free plan, while paid plans can opt out at any time and continue using Warp, including A…”
   • [claimed-docs] “Read a complete list of all the telemetry events that get sent for app analytics ... Opt out of telemetry at any time”
   • [claimed-docs] “Opt out of telemetry at any time”
   • [claimed-docs] “Monitor telemetry in real-time with Warp’s native Network Log * Opt out of telemetry at any time”
   • [community] “They have also innovated by requiring login (into a console!!)... Today they have heaps of telemetry, so a privacy nightmare. This is a term…”

   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 drawn
   Warp—none0/10

   No evidence in the pack mentions a terminal graphics protocol (e.g., Sixel, Kitty graphics protocol, iTerm2 inline images) or inline image/rich graphics rendering in Warp's terminal. Evidence only covers AI agents, MCP, telemetry, themes, and session restoration.

   ⚑ 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 Warp
   Warp~partialcommunity5/10

   Evidence shows Warp exposes platform-specific keybindings for macOS, Windows, and Linux (docs-49), a settings file enabling config portability across devices (docs-40), and CLI/agent components that work over SSH in any terminal (docs-59), implying cross-platform availability. However, there is no explicit doc confirming identical native app experience on all three OSes, and community reports describe Warp being broken specifically under WSL/Windows-via-SSH scenarios (warp-comm-10), undercutting a seamless 'same terminal, same config' experience. missing for 10: explicit first-party confirmation of feature parity across macOS/Linux/Windows, documented config-sync mechanism beyond a settings file, and independent corroboration that the same setup truly works identically on all three platforms.

   • [claimed-docs] “Open the **Conversations menu** (`⌘+Y` on macOS, `Ctrl+Shift+Y` on Windows/Linux), select a conversation, and then enter your query.”
   • [claimed-docs] “we are shipping a (long-overdue) settings file so that users and agents get programmatic control over settings and easy portability between …”
   • [claimed-docs] “Because it’s a regular command-line program, it works in any terminal emulator, including over SSH.”
   • [community] “Warp is so horribly broken right now and has been for weeks. Multiple github issues on consistent issue writing file. On top of that UI glit…”

   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 drawn
   Warp—none0/10

   Warp's docs mention running the `warp` agent CLI over SSH (warp-docs-3) but that's about launching an agent conversation, not the terminal itself carrying terminfo, shell integration, and config when SSHing into remote hosts. No evidence describes Warp's terminal propagating its shell integration/terminfo to remote hosts, and community reports (warp-comm-10, warp-comm-14) note broken functionality (file/diff explorer, code indexing) specifically over SSH connections, further indicating the core integration doesn't extend cleanly to remote sessions.

   • [claimed-docs] “Run the `warp` command to start a conversation in whichever terminal you already use, over SSH, or on a machine where Warp isn’t installed.”
   • [community] “Warp is so horribly broken right now and has been for weeks. Multiple github issues on consistent issue writing file. On top of that UI glit…”
   • [community] “Nearly everything about the experience of a terminal is better than iTerm though? Very nice having the terminal treated like a text file. It…”

   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 Alacritty
   Warp—none0/10

   The evidence pack contains no mention of tmux support, tmux control mode, or any documented native tmux integration in Warp's docs or community discussion — Warp's session/pane features (blocks, session restoration) are its own proprietary system, not tmux. Since terminal emulators are a fair category for this axis, absence of evidence yields 'none'.

   ⚑ 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 Warp
   Warp~partialprobed6/10

   Warp exposes a genuine programmatic surface — an OpenAPI spec (confirmed live at docs.warp.dev/openapi.json), an Oz CLI with API keys for headless/CI control, MCP as a plugin interface, and a documented Warp Agent CLI that spins up its own PTY so an agent can run commands, provide input, and control full-screen apps (warp-docs-69, warp-docs-24, warp-docs-32). This supports agent-driven terminal automation, but the evidence never documents a protocol/API specifically for creating or managing Warp's terminal panes/windows or reading raw pane output — the API/CLI focus is on running and orchestrating agents rather than exposing the terminal UI itself as a controllable surface. Missing for 10: documented pane-creation/window-management API, explicit read-output API distinct from agent conversation transcripts, and independent/hands-on confirmation of external programmatic terminal control.

   • [claimed-docs] “API, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”
   • [claimed-docs] “It creates and maintains its own pseudoterminal (PTY), which lets you and the agent execute commands and interact with running processes thr…”
   • [claimed-docs] “You can run full-screen and interactive terminal apps like sqlite and python through the agent session. Warp Agent can also control those ap…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline. Use it to start …”

   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 drawn
   Warp—none0/10

   Warp's extensibility is centered on MCP servers (for extending AI agent tool access) and a settings file, not a general-purpose scripting/plugin language like Lua or Python for customizing terminal behavior (e.g., kitty-style 'kittens'). No evidence pack item documents a scripting API, plugin SDK, or embedded language runtime for extending the terminal itself.

   • [claimed-docs] “MCP servers extend Warp’s local agents in a modular, flexible way by exposing custom tools or data sources through a standardized interface …”
   • [claimed-docs] “we are shipping a (long-overdue) settings file so that users and agents get programmatic control over settings and easy portability between …”

   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 drawn
   Warp—none0/10

   Warp documents automatic session restoration (windows/tabs/panes reopened on relaunch) but this is a global auto-restore behavior, not a user-authored config/script that defines named per-project startup layouts launchable via one command. No evidence of a project-workspace/layout definition file or CLI flag to open a specific named session.

   • [claimed-docs] “Restore your windows, tabs, panes, and recent Blocks automatically when you relaunch Warp.”
   • [claimed-docs] “Session restoration allows you to quickly pick up where you left off in your previous terminal session.”

   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 drawn
   Warp~partialclaimed5/10

   Warp ships documented CLI/IPC surfaces — the standalone Warp Agent CLI (works in any terminal, over SSH, creates its own PTY, can run/control full-screen apps) and the Oz CLI for running/managing cloud agents from scripts or CI with API-key auth — giving real command-line scriptability of agent sessions. However, the evidence is agent-centric (starting conversations, running commands, controlling processes) rather than direct terminal-window primitives like opening/arranging windows or querying pane/window state as the story literally describes (tmux/iTerm2-style control). Missing for 10: explicit documented commands to open/manage Warp windows or panes, send raw text to a specific pane, or query terminal UI state independent of an agent session; independent hands-on confirmation of such scripting.

   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.”
   • [claimed-docs] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline. Use it to start …”
   • [claimed-docs] “With the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers lik…”
   • [claimed-docs] “API Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and co…”
   • [claimed-docs] “Because it’s a regular command-line program, it works in any terminal emulator, including over SSH.”
   • [claimed-docs] “It creates and maintains its own pseudoterminal (PTY), which lets you and the agent execute commands and interact with running processes thr…”
   • [claimed-docs] “The Warp Agent CLI lets you switch directories while in an agent session, and even run agents on remote machines without installing remote b…”
   • [claimed-docs] “The Warp Agent is now available as a standalone CLI that you can use anywhere – Ghostty, iTerm 2, VS Code, built-in Windows and Mac Terminal…”

   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 Warp
   Warp~partialcommunity4/10

   Only evidence is a community anecdote naming notifications on long-running command completion as a favorite feature; there is no first-party documentation confirming exit status display, command duration tracking, or notification configuration as shell-integration features (the docs pack is dominated by AI/agent capabilities instead). missing for 10: official docs on exit status indicators, duration display, and notification settings; independent corroboration beyond a single forum comment.

   • [community] “My daily driver for a few months now, even after trying Rio/Ghostty/Wezterm... Favorite feature is the notification when a long running comm…”

   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 drawn
   Warp—none0/10

   The evidence pack references Warp's 'Blocks' concept (grouping commands and output) and session restoration of blocks, but never documents a shell-integration feature for jumping/navigating between prompt marks or command blocks in scrollback via keyboard shortcuts. Missing for 10: explicit documentation of prompt/command mark navigation shortcuts, scrollback jump-to-previous/next-prompt functionality, and any shell-integration-specific navigation UI.

   • [claimed-docs] “Restore your windows, tabs, panes, and recent Blocks automatically when you relaunch Warp.”
   • [claimed-docs] “Session restoration allows you to quickly pick up where you left off in your previous terminal session.”
   • [claimed-docs] “Sometimes, you may want to prevent a sensitive Block from being saved on your computer, or you may want to clear blocks from a machine entir…”

   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 Warp
   Warp~partialclaimed5/10

   Warp Drive lets users save workflows and run them 'on-demand' (warp-docs-11, warp-docs-30), and AI Command Suggestions via '#' provide natural-language command discovery (warp-docs-8), which together approximate a command-palette-style workflow, but no evidence explicitly describes a searchable palette UI for discovering and running arbitrary terminal actions. Missing for 10: explicit documentation of a dedicated command palette (e.g., Cmd+P style fuzzy search across commands/workflows), independent/community confirmation of this specific feature, and clarity on scope (built-in commands vs only saved workflows).

   • [claimed-docs] “Warp lets you save your most important workflows in Warp Drive so you can run them on‑demand or share with your team.”
   • [claimed-docs] “Warp lets you save your most important workflows in Warp Drive so you can run them on‑demand or share with your team. Let Warp AI handle the…”
   • [claimed-docs] “Type '#' on your command line and start describing the command you want to run using natural language. Warp will load AI Command 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 Alacritty
   Warp—none0/10

   The evidence pack contains no documentation or community mention of clickable URLs/file paths, keyboard-selectable links, or similar output-navigation features in Warp's terminal Blocks. This is a fair ergonomics question for a terminal product but nothing in the pack confirms it ships.

   ⚑ 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 to Alacritty
   Warp—none0/10

   The evidence pack covers Warp's AI/agent features, session restoration, theming, and telemetry, but contains no mention of scrollback search or match navigation functionality, despite this being a reasonable and expected axis for any terminal emulator.

   ⚑ 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