Warp vs WezTerm

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

   WezTerm—none0/10

   WezTerm is a terminal emulator with no llms.txt or agent-oriented documentation endpoint; probes explicitly confirm 404s for llms.txt and markdown doc variants, and there is no mention of agent-facing docs anywhere in the docs or community evidence.

   • [probe] “PROBE llms.txt: HTTP 404 at https://wezterm.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://wezterm.org/features.html.md”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   WezTerm✓fullprobed8/10

   The CLI subcommand explicitly documents spawning/manipulating panes on a running instance, and a hands-on runtime probe confirms a fully headless control loop (mux-server --daemonize, cli spawn, send-text, get-text, list) with no GUI session required — directly matching the CI/automation story. Missing for 10: explicit first-party CI documentation/examples and independent community reports of using WezTerm in CI pipelines.

   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “official CLI documented at https://wezterm.org/cli/cli/index.html”

   proof ↗⚑ 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

   WezTerm—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 drawn
   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

   WezTerm✓fullprobed8/10

   WezTerm ships an official `wezterm cli` subcommand documented for spawning programs, sending text, reading pane content, and manipulating tabs/panes/windows, and a runtime probe confirms it works fully headless (mux-server daemonized, spawn/send-text/get-text/list all functioning without a GUI) — exactly the kind of scriptable, agent-drivable CLI an AI-native user would need. Missing for 10: no explicit first-party framing or examples for AI/agent orchestration use-cases, and no independent (non-vendor) confirmation beyond the single runtime probe.

   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “official CLI documented at https://wezterm.org/cli/cli/index.html”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”

   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

   WezTerm~partialprobed6/10

   WezTerm exposes a documented CLI (wezterm cli spawn/send-text/get-text/list) and a Lua config API, and a runtime probe confirms headless scripted control works end-to-end without a GUI, which is strong evidence for programmatic/agentic driving. However this is a CLI/Lua surface rather than a formal public API spec, and explicit machine-readable API docs (llms.txt, OpenAPI) both 404. missing for 10: an official structured API spec (OpenAPI/schema) or llms.txt for machine consumption, first-party documentation framing this as an 'AI-native' or agent-facing API, and independent third-party corroboration of scripted/agentic use beyond the single runtime probe.

   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “official CLI documented at https://wezterm.org/cli/cli/index.html”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://wezterm.org/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://wezterm.org/openapi.json, https://wezterm.org/swagger.json, https://wezterm.org/api/openapi.…”

   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

   WezTerm—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

   WezTerm—none0/10

   WezTerm provides CLI/mux scripting and headless control (spawn, send-text, get-text) that could be used as building blocks, but there is no evidence of a scheduler, trigger system, or persistent background automation framework that runs autonomously without an external orchestrator invoking it. missing for 10: any documented scheduling/trigger mechanism, autonomous background job execution, or agent-loop capability distinct from manual/CLI-invoked scripting.

   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [probe] “official CLI documented at https://wezterm.org/cli/cli/index.html”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Warp—none0/10

   Warp does expose an OpenAPI spec (warp-probe-2) and API/CLI reference docs (warp-docs-63, warp-probe-3), so the axis of an API reference applies given Warp's platform ambitions (warp-docs-42). However, there is no evidence of an interactive reference UI with runnable/'try it out' examples — the pack only shows a raw openapi.json file and static CLI reference pages, not an interactive explorer.

   • [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] “API, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.”

   proof ↗⚑ flag

   WezTerm—none0/10

   WezTerm is a terminal emulator with static configuration docs and a Lua API reference, but there's no evidence of an interactive, runnable-examples API reference; probes confirm no llms.txt, no docs-md, and no OpenAPI/interactive API surface exists.

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

   proof ↗⚑ flag

2. 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

   WezTerm—none0/10

   WezTerm exposes a CLI and mux protocol but no machine-readable API spec is documented; probes for llms.txt, docs-md, and OpenAPI/swagger endpoints all return 404.

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

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Warp—none0/10

   Warp exposes an API, CLI, SDK, and MCP platform (warp-docs-42, warp-probe-2 openapi.json), so API versioning is a fair axis, but no evidence pack item documents API version numbers, a changelog, or any formal deprecation policy for these interfaces.

   • [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”

   proof ↗⚑ flag

   WezTerm—none0/10

   No evidence of a versioned API or documented deprecation policy; probes for llms.txt, docs-md, and OpenAPI specs all returned 404, and no docs mention API versioning or deprecation practices. WezTerm's Lua config API and CLI have no documented stability/versioning guarantees in the evidence pack.

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

   proof ↗⚑ 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

   WezTerm—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

   WezTerm—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 userPerform bulk operations across many items at once

   weight 2 · round to Warp
   Warp~partialclaimed6/10

   Warp supports running many agents concurrently across repos/tasks (warp-docs-28), cloud agents triggered by schedules/webhooks at scale (warp-docs-4, warp-docs-5, warp-docs-60), and a 'software factory' pattern coordinating a fleet of agents into mergeable PRs (warp-docs-68), which together support bulk/parallel operations across many items. However, there is no explicit documentation of a UI or command for batch-selecting many items (files, repos, tasks) and applying one operation across all of them in a single bulk action, nor independent/hands-on evidence confirming this scales well in practice. missing for 10: concrete bulk-selection/batch-apply UI or command, first-party docs quantifying scale limits, independent verification that parallel/bulk agent runs work reliably at scale.

   • [claimed-docs] “Parallelism: Run many agents concurrently across repos or tasks”
   • [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] “A software factory takes in requests (bug reports, feature specs, support escalations), and a coordinated fleet of agents works them into a …”
   • [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] “The Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.”

   proof ↗⚑ flag

   WezTerm~partialprobed4/10

   WezTerm's CLI (`wezterm cli list/spawn/send-text/get-text`) exposes scriptable primitives that let a user enumerate and act on multiple panes/tabs/windows programmatically, and the runtime probe confirms headless multiplexer control works end-to-end. However, there's no evidence of a native 'bulk operation' command that targets many items in a single call — any bulk behavior would require external shell scripting/looping over the CLI primitives, which isn't documented. Missing for 10: documented batch/multi-target commands, evidence of scaling to large numbers of panes/tabs, and any built-in bulk-action feature beyond single-target CLI calls.

   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [probe] “official CLI documented at https://wezterm.org/cli/cli/index.html”

   proof ↗⚑ flag

2. 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

   WezTerm~partialprobed3/10

   WezTerm's docs show scripted automation hooks (CLI to spawn/manipulate panes headlessly, shell-integration user vars, and automatic config-reload on file change) that could be used to script reactive behavior, but there is no explicit documentation of a rule/event system (e.g., named event triggers or pattern-based action bindings) that fires automatically on terminal events. Missing for 10: explicit event-trigger/rule API documentation, examples of event-based automation, and independent confirmation that users define event-driven rules.

   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded”
   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded and the majority of o…”
   • [claimed-docs] “The shell integration provides a shell function named __wezterm_set_user_var which can be used to set your own user vars.”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”

   proof ↗⚑ flag

3. 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

   WezTerm—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 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

   WezTerm—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 WezTerm
   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

   WezTerm✓fullcommunity9/10

   WezTerm's config is plain Lua text (wezterm.lua) that lives in dotfiles, auto-reloads on change, and supports CLI overrides — and community evidence directly confirms this makes cross-machine syncing trivial ('it's just Lua code, easy to diff and easy to apply' vs. iTerm2 where syncing was 'next to impossible'). Missing for 10: no first-party doc explicitly discussing dotfiles/multi-machine sync workflows, only community corroboration.

   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded”
   • [claimed-docs] “wezterm allows overriding configuration values via the command line”
   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded and the majority of o…”
   • [community] “What killed iTerm2 for me was the fact that syncing settings between machines with chezmoi was next to impossible. With Wezterm it's just Lu…”

   proof ↗⚑ flag

Fonts

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

   weight 2 · round to WezTerm
   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

   WezTerm!disputedcontradicted6/10

   WezTerm's docs explicitly advertise ligatures, color emoji, and font fallback with true color, and config docs mention font-size/color-scheme tuning and live-reload of config changes, supporting fine-grained font control. However, hands-on community reports concretely contradict the polish of this: one user found WezTerm 'severely lacking in font configuration department contrary to popular opinion,' and another reports it 'renders Pragmata Pro Mono Liga much worse on Linux than Tilix does,' plus a Windows user found ligature rendering came with worse input latency than alternatives. Missing for 10: first-party deep-dive docs on fallback font ordering/fine-tuning knobs beyond font_size, and independent corroboration resolving the rendering-quality complaints.

   • [claimed-docs] “Ligatures, Color Emoji and font fallback, with true color and dynamic color schemes”
   • [claimed-docs] “Ligatures, Color Emoji and font fallback, with true color and dynamic color schemes.”
   • [claimed-docs] “changing the font size and color scheme.”
   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded and the majority of o…”
   • [community] “I live inside tmux inside alacritty running wsl. I tried wezterm after reading all the great reviews... and i found it severely lacking in f…”
   • [community] “It renders Pragmata Pro Mono Liga much worse on Linux than Tilix does. Otherwise, I'd give it a shot.”
   • [community] “I tried WezTerm on Windows because I was looking for a terminal with ligature support and lower input latency than Windows Terminal. Unfortu…”

   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

   WezTerm~partialclaimed4/10

   Evidence confirms WezTerm supports configurable color schemes and dynamic color scheme changes via config/live-reload, but nothing in the pack explicitly documents automatic OS light/dark mode detection or a scheme-switching mechanism tied to system appearance. Missing for 10: explicit documentation of automatic light/dark mode switching (e.g., appearance-based scheme selection), and independent confirmation it works in practice.

   • [claimed-docs] “Ligatures, Color Emoji and font fallback, with true color and dynamic color schemes”
   • [claimed-docs] “changing the font size and color scheme.”
   • [claimed-docs] “Ligatures, Color Emoji and font fallback, with true color and dynamic color schemes.”
   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded and the majority of o…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   WezTerm~partialprobed6/10

   WezTerm ships a genuine CLI/mux API (`wezterm cli spawn/send-text/get-text/list`) that a hands-on probe confirms works fully headless without a GUI session, covering pane/tab/window manipulation and text I/O — a strong basis for AI-native control. However, there's no evidence of full UI/API parity (e.g. scripting quick-select, font/color-scheme changes, image protocol, or search-mode equivalents via CLI), and no OpenAPI/machine-readable API surface (probes for openapi.json and llms.txt returned 404s), so many UI-only interactions remain unaddressed by the API. Missing for 10: documented CLI/Lua equivalents for all interactive UI features (quick select, scrollback search, image display, appearance changes), and any formal API spec.

   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://wezterm.org/openapi.json, https://wezterm.org/swagger.json, https://wezterm.org/api/openapi.…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://wezterm.org/llms.txt”

   proof ↗⚑ flag

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

   weight 3 · round to WezTerm
   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

   WezTerm~partialcommunity5/10

   WezTerm's configuration is plain-text Lua stored locally (not locked in a proprietary format or cloud service), and community evidence shows scrollback/session content can be dumped via `wezterm cli get-text`, giving a de facto path to extract your data and leave. However, there is no explicit documented 'export all data' feature, no bundled data-portability tool, and no discussion of migrating multiplexer session state elsewhere. Missing for 10: an explicit export/backup feature or documentation addressing full data portability beyond config files and scrollback dumps, and independent confirmation of leaving with all state intact.

   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded”
   • [claimed-docs] “wezterm allows overriding configuration values via the command line”
   • [community] “One thing I was looking for just yesterday was a way to dump my terminal's scrollback - escape sequences and all - to stdout... wezterm does…”
   • [community] “What killed iTerm2 for me was the fact that syncing settings between machines with chezmoi was next to impossible. With Wezterm it's just Lu…”

   proof ↗⚑ flag

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

   weight 2 · round to Warp
   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

   WezTerm—none0/10

   No evidence in the pack references WezTerm's source license, GitHub repository, or open-source licensing terms; all citations concern terminal features, CLI usage, and user reviews, not code openness. Missing for 10: mention of the repository/license, license type (e.g. MIT), or any statement about source availability.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to WezTerm
   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

   WezTerm✓fullprobed8/10

   WezTerm ships an embedded mux server that users can run themselves (self-hosted) and connect to via SSH domains, with docs on multiplexing and SSH domains plus a runtime probe confirming a fully headless `wezterm-mux-server --daemonize` control loop with `wezterm cli` spawn/send-text/get-text/list working without a GUI session. missing for 10: independent/community confirmation of self-hosted mux server usage specifically (most community quotes discuss desktop terminal use, not self-hosted server operation), and explicit licensing/deployment guidance for running it as a persistent self-hosted service.

   • [claimed-docs] “A connection to a remote wezterm multiplexer made via an ssh connection is referred to as an _SSH domain_.”
   • [claimed-docs] “wezterm uses an embedded ssh library to provide an integrated SSH client. The client can be used to make ad-hoc SSH connections to remote ho…”
   • [claimed-docs] “Take a look at the multiplexing section for an alternative configuration that connects to a remote wezterm instance and preserves your tabs.”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”

   proof ↗⚑ flag

Multiplexing

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

   weight 3 · round to WezTerm
   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

   WezTerm✓fullprobed9/10

   WezTerm natively multiplexes panes, tabs, and windows locally and remotely with CLI control and persistent mux server, and multiple hands-on community reports confirm fast, responsive pane splitting used as a tmux replacement. missing for 10: no independent third-party benchmark comparing full multiplexer feature parity (session detach/reattach robustness) across platforms.

   • [claimed-docs] “Multiplex terminal panes, tabs and windows on local and remote hosts, with native mouse and scrollback”
   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [community] “The main feature for me is splitting panes... The Lua configuration is very intuitive as well. I do get some indirect crashes when Xwayland …”
   • [community] “I finally went back and gave wezterm a serious try... The mouse issues I was seeing go away. Splitting panes and resizing lots of panes is f…”
   • [community] “I have been able to completely replace tmux with wezterm on Linux and Mac and love it. It even works on Windows.”

   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

   WezTerm—none0/10

   No evidence in the pack of a global-hotkey summon or quake-style dropdown window feature; documentation covers panes/tabs/multiplexing, SSH, CLI control, and scrollback but never mentions an instant-summon/dropdown mode, and no community citation confirms this capability exists.

   ⚑ 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

   WezTerm~partialclaimed3/10

   WezTerm's mux-server/SSH-domain feature lets tabs and panes survive a GUI crash or restart by reconnecting to a persistent multiplexer instance, and OSC7-based cwd tracking lets new tabs inherit a working directory — but these require manually setting up a separate mux-server domain rather than being an automatic 'restore my session' feature, and there's no evidence of full window-layout or automatic state persistence on plain restart. Missing for 10: documented automatic session/workspace save-and-restore across app restarts, evidence of working-directory restoration (not just inheritance) after crash, and independent confirmation the mux-domain workflow reliably recovers full window/tab state.

   • [claimed-docs] “A connection to a remote wezterm multiplexer made via an ssh connection is referred to as an _SSH domain_.”
   • [claimed-docs] “Take a look at the multiplexing section for an alternative configuration that connects to a remote wezterm instance and preserves your tabs.”
   • [claimed-docs] “When the current working directory has been set via OSC 7, spawning a new tab will use the current working directory of the current tab, so …”
   • [claimed-docs] “wezterm uses an embedded ssh library to provide an integrated SSH client. The client can be used to make ad-hoc SSH connections to remote ho…”

   proof ↗⚑ flag

Benchmarks

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

   weight 2 · round drawn
   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

   WezTerm—none0/10

   No evidence pack item shows WezTerm publishing formal benchmarks, latency/throughput measurements, or comparative performance data; docs only list features, and community comments are anecdotal impressions (some praising speed, others reporting higher latency than cmd.exe/kitty/alacritty) rather than measured numbers.

   ⚑ flag

Rendering

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

   weight 3 · round to WezTerm
   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

   WezTerm!disputedcontradicted4/10

   WezTerm's docs tout GPU-based rendering features (ligatures, true color, dynamic schemes) and community reports frequently praise it as fast/responsive (e.g., wezterm-comm-3, wezterm-comm-4, wezterm-comm-5), but multiple hands-on reports directly contradict sustained performance under heavy output — lag when scrolling long lists (wezterm-comm-11), higher input latency than Kitty/cmd.exe and blank-line rendering glitches in vim (wezterm-comm-6, wezterm-comm-12), and poor font rendering vs other GPU terminals (wezterm-comm-18). Missing for 10: explicit first-party GPU-rendering documentation/benchmarks and resolution of the latency/rendering-glitch reports.

   • [claimed-docs] “Ligatures, Color Emoji and font fallback, with true color and dynamic color schemes”
   • [claimed-docs] “Ligatures, Color Emoji and font fallback, with true color and dynamic color schemes.”
   • [community] “Recently switched to WezTerm and I'm very happy... WezTerm is leaps and bounds better in terms of what comes out-of-the-box. My terminal con…”
   • [community] “I finally went back and gave wezterm a serious try... The mouse issues I was seeing go away. Splitting panes and resizing lots of panes is f…”
   • [community] “WezTerm is just so much faster than iTerm2, wish I had switched sooner!”
   • [community] “I tried WezTerm on Windows because I was looking for a terminal with ligature support and lower input latency than Windows Terminal. Unfortu…”
   • [community] “Downloaded the latest stable for macOS and still has the same problem as before - if you have long list of items you want to scroll through …”
   • [community] “I really wanted WezTerm to be the best terminal on macOS. However...WezTerm's latency was noticeably higher than Kitty and WezTerm often pai…”
   • [community] “It renders Pragmata Pro Mono Liga much worse on Linux than Tilix does. Otherwise, I'd give it a shot.”

   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

   WezTerm—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

Graphics

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

   weight 2 · round to WezTerm
   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

   WezTerm!disputedcontradicted6/10

   WezTerm documents iTerm2-compatible inline image protocol support plus a built-in imgcat CLI for outputting images to the terminal, which is a genuine documented graphics protocol implementation. However, a hands-on community report states the image support 'didn't play well with tmux,' a concrete real-world failure that led a user to switch away, contradicting a fully seamless graphics experience. Missing for 10: independent hands-on confirmation that images render cleanly outside tmux edge cases, and evidence of broader protocol support (e.g., Sixel/Kitty graphics) beyond iTerm2 compatibility.

   • [claimed-docs] “Output an image to the terminal”
   • [claimed-docs] “iTerm2 compatible image protocol support, and built-in imgcat command”
   • [community] “The thing that made me switch to Ghostty was the image support in wez didn't play well with tmux. After testing wez, kitty, and Ghostty, I e…”

   proof ↗⚑ flag

Platforms

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

   weight 2 · round to WezTerm
   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

   WezTerm✓fullcommunity8/10

   WezTerm's Lua-based config is designed to be portable, with docs describing config file watching/reloading and command-line overrides, and community evidence confirms real cross-platform parity: "I have been able to completely replace tmux with wezterm on Linux and Mac... It even works on Windows" and a user reporting seamless config sync across machines via chezmoi/Lua. macOS install via brew is explicitly documented. Missing for 10: explicit first-party install docs/citations for Linux and Windows in this pack (only macOS install doc present), and no direct doc statement guaranteeing identical behavior across all three OSes.

   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded”
   • [claimed-docs] “wezterm allows overriding configuration values via the command line”
   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded and the majority of o…”
   • [claimed-docs] “WezTerm is available for brew users”
   • [claimed-docs] “$ brew install --cask wezterm”
   • [community] “I have been able to completely replace tmux with wezterm on Linux and Mac and love it. It even works on Windows.”
   • [community] “What killed iTerm2 for me was the fact that syncing settings between machines with chezmoi was next to impossible. With Wezterm it's just Lu…”

   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 WezTerm
   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

   WezTerm~partialclaimed6/10

   WezTerm ships a built-in SSH client and 'SSH domains' that let you multiplex tabs/panes over an SSH connection to a remote wezterm mux, and it exposes shell-integration features (OSC7 cwd tracking, user vars) for local sessions, but the evidence never explicitly confirms that terminfo, shell-integration scripts, or local config are automatically propagated/carried to the remote host on ad-hoc SSH connections (docs-9/14/18 note an 'alternative configuration' needed for full tab/pane preservation, implying the basic ad-hoc SSH mode doesn't fully carry everything). missing for 10: explicit documentation/evidence of terminfo propagation to remote host, confirmation that shell-integration scripts/config are auto-installed or carried over plain SSH (not just via the multiplexer/domain setup), and independent hands-on confirmation of this remote workflow working smoothly.

   • [claimed-docs] “wezterm uses an embedded ssh library to provide an integrated SSH client. The client can be used to make ad-hoc SSH connections to remote ho…”
   • [claimed-docs] “A connection to a remote wezterm multiplexer made via an ssh connection is referred to as an _SSH domain_.”
   • [claimed-docs] “Take a look at the multiplexing section for an alternative configuration that connects to a remote wezterm instance and preserves your tabs.”
   • [claimed-docs] “wezterm uses an embedded ssh library to provide an integrated SSH client.”
   • [claimed-docs] “When the current working directory has been set via OSC 7, spawning a new tab will use the current working directory of the current tab, so …”
   • [claimed-docs] “The shell integration provides a shell function named __wezterm_set_user_var which can be used to set your own user vars.”

   proof ↗⚑ flag

Tmux

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

   weight 2 · round to WezTerm
   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

   WezTerm~partialprobed6/10

   WezTerm documents its own native multiplexing (panes/tabs/windows, SSH domains, mux server, cli spawn/send-text/get-text control mode verified in a headless probe) as a built-in alternative to tmux, and users can also run tmux inside it. However, this is WezTerm's own multiplexer, not a documented tmux control-mode/integration, and community evidence shows friction when combining WezTerm with actual tmux (image protocol issues causing a user to switch to Ghostty). missing for 10: explicit documentation of tmux control-mode (tmux -CC) support or a first-party statement about compatibility/integration with tmux itself, and resolution of the tmux+image-support conflict noted by a user.

   • [claimed-docs] “Multiplex terminal panes, tabs and windows on local and remote hosts, with native mouse and scrollback”
   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “A connection to a remote wezterm multiplexer made via an ssh connection is referred to as an _SSH domain_.”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [community] “I have been able to completely replace tmux with wezterm on Linux and Mac and love it. It even works on Windows.”
   • [community] “The thing that made me switch to Ghostty was the image support in wez didn't play well with tmux. After testing wez, kitty, and Ghostty, I e…”

   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 WezTerm
   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

   WezTerm✓fullprobed9/10

   WezTerm documents a CLI subcommand (wezterm cli) that can spawn programs, manipulate tabs/panes, and read pane text (get-text), and a runtime probe confirms an agent-driven headless workflow: spawning panes, sending text/commands, and reading output via a mux server with no GUI required. This is a documented, hands-on-verified programmatic control protocol suitable for an AI agent to drive the terminal. Missing for 10: no formal OpenAPI/RPC schema (llms.txt and openapi probes 404) and no first-party example of an AI agent integration specifically.

   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “official CLI documented at https://wezterm.org/cli/cli/index.html”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [community] “One thing I was looking for just yesterday was a way to dump my terminal's scrollback - escape sequences and all - to stdout... wezterm does…”

   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 WezTerm
   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

   WezTerm~partialcommunity6/10

   WezTerm's configuration and extensibility system is Lua-based, confirmed by community reports (e.g., 'with Wezterm it's just Lua code, easy to diff and easy to apply') and supported by docs showing config-file hooks, live-reload, CLI overrides, and user-variable functions that imply a scripting surface beyond simple config. However, the evidence pack lacks direct first-party documentation explicitly describing the Lua API/plugin system, and there is no support for Python or kitten-style extensions (those are a different terminal's feature) — missing for 10: explicit docs citation of the Lua scripting/plugin API, evidence of a plugin ecosystem, and any Python/kittens equivalent.

   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded”
   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded and the majority of o…”
   • [claimed-docs] “The shell integration provides a shell function named __wezterm_set_user_var which can be used to set your own user vars.”
   • [community] “What killed iTerm2 for me was the fact that syncing settings between machines with chezmoi was next to impossible. With Wezterm it's just Lu…”

   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 WezTerm
   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

   WezTerm✓fullprobed7/10

   WezTerm's Lua-based config supports scripting startup behavior, and the documented `cli` subcommand can spawn programs and manipulate tabs/panes; a hands-on probe confirms a fully headless control loop (spawn window, send commands, enumerate panes) without GUI interaction, which is exactly the kind of single-command scripted session/layout setup the story describes. Missing for 10: explicit vendor documentation of a named 'workspace' or multi-pane layout template feature (e.g. gui-startup event) and independent community confirmation specifically of launching complex multi-window/pane project layouts via one script.

   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded”
   • [claimed-docs] “wezterm will watch the config file that it loads; if/when it changes, the configuration will be automatically reloaded and the majority of o…”
   • [claimed-docs] “wezterm allows overriding configuration values via the command line”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”

   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 WezTerm
   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

   WezTerm✓fullprobed9/10

   WezTerm ships a documented `cli` subcommand (spawn, send-text, get-text, list, activate, etc.) that controls a running GUI or multiplexer instance, and this was independently verified headless (daemonized mux server + spawn/send-text/get-text/list roundtrip) plus corroborated by a community user dumping scrollback via get-text. Missing for 10: no first-party mention of a richer structured IPC/JSON-RPC protocol beyond the CLI wrapper, and no independent third-party write-up beyond the single HN mention.

   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “The cli subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and p…”
   • [probe] “official CLI documented at https://wezterm.org/cli/cli/index.html”
   • [probe] “PROBE runtime (recorded 2026-09-04, wezterm 20240203 via brew cask): fully headless control loop verified — `wezterm-mux-server --daemonize`…”
   • [community] “One thing I was looking for just yesterday was a way to dump my terminal's scrollback - escape sequences and all - to stdout... wezterm does…”

   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

   WezTerm—none0/10

   WezTerm's shell-integration docs describe OSC 7 cwd-tracking and custom user vars (wezterm-docs-10, wezterm-docs-20, wezterm-docs-25), but the evidence pack contains no mention of exit-status tracking, command duration, or notifications when long-running commands finish — features other terminals' shell integrations advertise. Missing for 10: documented exit-status capture, command-duration timing, and completion notifications.

   • [claimed-docs] “When the current working directory has been set via OSC 7, spawning a new tab will use the current working directory of the current tab, so …”
   • [claimed-docs] “spawning a new tab will use the current working directory of the current tab, so that you don't have to manually change the directory”
   • [claimed-docs] “The shell integration provides a shell function named __wezterm_set_user_var which can be used to set your own user vars.”

   proof ↗⚑ 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

   WezTerm—none0/10

   Evidence pack's shell-integration docs (wezterm-docs-10, wezterm-docs-20, wezterm-docs-25) only cover OSC 7 working-directory tracking and custom user vars — there is no mention of OSC 133 semantic prompt/command marks or any keybinding/feature to jump between prompts or command outputs in scrollback. Missing for 10: documentation or evidence of prompt-jump/command-mark navigation, keybindings for 'jump to previous/next prompt', and any independent confirmation of this specific capability.

   • [claimed-docs] “When the current working directory has been set via OSC 7, spawning a new tab will use the current working directory of the current tab, so …”
   • [claimed-docs] “spawning a new tab will use the current working directory of the current tab, so that you don't have to manually change the directory”
   • [claimed-docs] “The shell integration provides a shell function named __wezterm_set_user_var which can be used to set your own user vars.”

   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

   WezTerm—none0/10

   The evidence pack documents CLI subcommands, quick-select, scrollback search, and SSH/multiplexing features, but nowhere mentions a searchable command palette for discovering/running actions. A community comment even notes that WezTerm's many features 'are not really discoverable,' reinforcing the absence of such a UI. Missing for 10: any documentation or user report of a command-palette UI, its keybinding, or its action list.

   • [community] “my only complaint is that its many features are not really discoverable. Sure, the documentation is really good, and the author is very enga…”
   • [claimed-docs] “The _cli_ subcommand interacts with a running wezterm GUI or multiplexer instance, and can be used to spawn programs and manipulate tabs and…”
   • [claimed-docs] “Quick Select mode allows you to quickly highlight text that matches commonly copied patterns, select a match by typing a one-or-two characte…”

   proof ↗⚑ flag

Hyperlinks

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

   weight 2 · round to WezTerm
   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

   WezTerm~partialclaimed4/10

   WezTerm's Quick Select mode lets users highlight and copy commonly-matched text patterns via keyboard shortcuts, which could cover URLs/paths, but the evidence pack never explicitly documents clickable URL/file opening or an 'open with' action, nor mouse-click-to-open behavior. missing for 10: explicit doc on clicking URLs/paths to open them, evidence of file-path recognition, independent confirmation of click-to-open working in practice.

   • [claimed-docs] “Quick Select mode allows you to quickly highlight text that matches commonly copied patterns, select a match by typing a one-or-two characte…”
   • [claimed-docs] “Searchable Scrollback (use mouse wheel and `Shift-PageUp` and `Shift PageDown` to navigate, Ctrl-Shift-F to activate search mode)”

   proof ↗⚑ flag

Scrollback

1. developerSearch my scrollback quickly and jump between matches

   weight 2 · round to WezTerm
   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

   WezTerm✓fullcommunity8/10

   WezTerm documents a Searchable Scrollback feature with Ctrl-Shift-F search mode and keyboard navigation (Shift-PageUp/PageDown, mouse wheel), directly matching the story of quickly searching and jumping between matches; Quick Select mode further complements this for jumping to specific text patterns. Community evidence corroborates related scrollback tooling (get-text dump) though no direct hands-on account of search-and-jump-between-matches UX specifically. Missing for 10: independent hands-on account of the search-mode match-navigation experience (e.g., keybindings for next/prev match) and any friction/limitations reported by users.

   • [claimed-docs] “Searchable Scrollback (use mouse wheel and `Shift-PageUp` and `Shift PageDown` to navigate, Ctrl-Shift-F to activate search mode)”
   • [claimed-docs] “Searchable Scrollback (use mouse wheel and Shift-PageUp and Shift PageDown to navigate, Ctrl-Shift-F to activate search mode)”
   • [claimed-docs] “Quick Select mode allows you to quickly highlight text that matches commonly copied patterns, select a match by typing a one-or-two characte…”
   • [community] “One thing I was looking for just yesterday was a way to dump my terminal's scrollback - escape sequences and all - to stdout... wezterm does…”

   proof ↗⚑ flag