Skip to content

How Warp’s scores are calculated

The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.

verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10

PA Score53/100

Agent-ready 64.8 × 0.30 = 19.44

API quality 22.9 × 0.20 = 4.58

Openness 35.8 × 0.20 = 7.16

Built-in AI 83.3 × 0.15 = 12.49

Automation 62.0 × 0.15 = 9.30

(19.44 + 4.58 + 7.16 + 12.49 + 9.30) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 52.97 ÷ 1.00 = 53.0

Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.

Agent-ready64.8/100×0.30 of the PA blend

Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

  • [probe] https://docs.warp.dev/llms.txtPROBE llms.txt: HTTP 200 at https://docs.warp.dev/llms.txt # Warp > Documentation for Warp, the agentic development environment. Covers the Warp terminal, Warp agents, the Automa
  • [claimed-docs] https://docs.warp.dev/_llms-txt/code.txtWarp comes with a native code editor designed for quick, in-flow edits alongside your Agent conversations... with essentials like syntax highlighting, a tabbed file viewer, find and replace, Vim keybindings, and a file tree
  • [claimed-docs] https://docs.warp.dev/_llms-txt/warp-agent-cli.txtBecause it’s a regular command-line program, it works in any terminal emulator, including over SSH.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtopen the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/knowledge-and-collaboration.txtThe Admin Panel gives team administrators centralized control over organization-wide Warp settings, including agent autonomy, privacy controls, billing limits, codebase indexing, and sharing policies.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/factories.txtA software factory takes in requests (bug reports, feature specs, support escalations), and a coordinated fleet of agents works them into a stream of mergeable pull requests instead of a growing backlog.

Run the product headlessly / in CI for automationweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.warp.dev/reference/cliThe Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe 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 agents locally or in the cloud, connect MCP servers, configure integrations, and authenticate without requiring the Warp desktop app.
  • [claimed-docs] https://docs.warp.dev/reference/cliWith the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers like GitHub and Linear
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/warp-agent-cli.txtBecause it’s a regular command-line program, it works in any terminal emulator, including over SSH.
  • [claimed-docs] https://www.warp.dev/blog/introducing-the-warp-agent-cli-coding-agentThe Warp Agent CLI lets you switch directories while in an agent session, and even run agents on remote machines without installing remote binaries.
  • [claimed-docs] https://docs.warp.devTriggers: React to events from Slack, Linear, GitHub, or custom webhooks
  • [claimed-docs] https://docs.warp.devSchedules: Run recurring tasks like dependency updates or dead code removal
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.

Plug MCP servers into this product so it can use their toolsweight 3

3 (weight) × 9 (quality) × 1.0 (full) = 27.0 of 30 max

  • [claimed-docs] https://www.warp.dev/warp-aiConnect Warp AI to any tool via the Model Context Protocol. Pull context from databases, APIs, docs, and internal services so the AI understands your full stack.
  • [claimed-docs] https://docs.warp.dev/knowledge-and-collaboration/mcpMCP servers extend Warp’s local agents in a modular, flexible way by exposing custom tools or data sources through a standardized interface — essentially acting as plugins for Warp.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe 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 agents locally or in the cloud, connect MCP servers, configure integrations, and authenticate without requiring the Warp desktop app.
  • [claimed-docs] https://docs.warp.dev/reference/cliWith the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers like GitHub and Linear
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAgent Profiles - Use agent profiles to control what the agent can access, how it behaves, and where it can act, including file access, command execution, and MCP server usage.

Connect an agent via an official MCP serverweight 3

n/a — not applicable to this product: excluded from numerator and denominator

  • [claimed-docs] https://www.warp.dev/warp-aiConnect Warp AI to any tool via the Model Context Protocol. Pull context from databases, APIs, docs, and internal services so the AI understands your full stack.
  • [claimed-docs] https://docs.warp.dev/knowledge-and-collaboration/mcpMCP servers extend Warp’s local agents in a modular, flexible way by exposing custom tools or data sources through a standardized interface — essentially acting as plugins for Warp.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe 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 agents locally or in the cloud, connect MCP servers, configure integrations, and authenticate without requiring the Warp desktop app.
  • [claimed-docs] https://docs.warp.dev/reference/cliWith the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers like GitHub and Linear

Use an official CLIweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.warp.dev/reference/cliThe Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.
  • [claimed-docs] https://www.warp.dev/blog/introducing-the-warp-agent-cli-coding-agentThe Warp Agent CLI lets you switch directories while in an agent session, and even run agents on remote machines without installing remote binaries.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe 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 agents locally or in the cloud, connect MCP servers, configure integrations, and authenticate without requiring the Warp desktop app.
  • [claimed-docs] https://www.warp.dev/blog/introducing-the-warp-agent-cli-coding-agentThe Warp Agent is now available as a standalone CLI that you can use anywhere – Ghostty, iTerm 2, VS Code, built-in Windows and Mac Terminals
  • [claimed-docs] https://docs.warp.dev/reference/cliWith the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers like GitHub and Linear
  • [claimed-docs] https://docs.warp.dev/_llms-txt/warp-agent-cli.txtBecause it’s a regular command-line program, it works in any terminal emulator, including over SSH.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/warp-agent-cli.txtIt creates and maintains its own pseudoterminal (PTY), which lets you and the agent execute commands and interact with running processes through the same terminal, including prompts and full-screen terminal apps.

Drive the product through a documented public APIweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

  • [claimed-docs] https://www.warp.devAPI, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.
  • [probe] https://docs.warp.dev/openapi.jsonPROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key
  • [probe] https://docs.warp.dev/reference/cliofficial CLI documented at https://docs.warp.dev/reference/cli
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe 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 agents locally or in the cloud, connect MCP servers, configure integrations, and authenticate without requiring the Warp desktop app.
  • [claimed-docs] https://docs.warp.dev/reference/cliWith the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers like GitHub and Linear

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAgent Profiles - Use agent profiles to control what the agent can access, how it behaves, and where it can act, including file access, command execution, and MCP server usage.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/knowledge-and-collaboration.txtThe Admin Panel gives team administrators centralized control over organization-wide Warp settings, including agent autonomy, privacy controls, billing limits, codebase indexing, and sharing policies.

Build against official SDKsweight 2

2 (weight) × 3 (quality) × 0.6 (partial) = 3.6 of 20 max

  • [claimed-docs] https://www.warp.devAPI, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.
  • [probe] https://docs.warp.dev/openapi.jsonPROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key
  • [probe] https://docs.warp.dev/llms.txtPROBE llms.txt: HTTP 200 at https://docs.warp.dev/llms.txt # Warp > Documentation for Warp, the agentic development environment. Covers the Warp terminal, Warp agents, the Automa

Subscribe to events via webhooksweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

  • [claimed-docs] https://docs.warp.devTriggers: React to events from Slack, Linear, GitHub, or custom webhooks
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.

Agent-ready = 116.6 ÷ 180 × 100 = 64.8

API quality22.9/100×0.20 of the PA blend

The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [probe] https://docs.warp.dev/openapi.jsonPROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key
  • [probe] https://docs.warp.dev/reference/cliofficial CLI documented at https://docs.warp.dev/reference/cli
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
  • [claimed-docs] https://www.warp.devAPI, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [probe] https://docs.warp.dev/openapi.jsonPROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key
  • [claimed-docs] https://www.warp.devAPI, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://www.warp.devAPI, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.
  • [probe] https://docs.warp.dev/openapi.jsonPROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key
  • [probe] https://docs.warp.dev/reference/cliofficial CLI documented at https://docs.warp.dev/reference/cli

API quality = 16.0 ÷ 70 × 100 = 22.9

Openness35.8/100×0.20 of the PA blend

Can you leave, inspect, or self-host — data export, open source, portability.

Do everything through the API that I can do in the UIweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://www.warp.devAPI, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate.
  • [claimed-docs] https://www.warp.devany surface — watch, steer, and hand off runs from web, mobile, terminal, or IDE.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe 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 agents locally or in the cloud, connect MCP servers, configure integrations, and authenticate without requiring the Warp desktop app.
  • [claimed-docs] https://docs.warp.dev/reference/cliWith the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers like GitHub and Linear
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAgent Profiles - Use agent profiles to control what the agent can access, how it behaves, and where it can act, including file access, command execution, and MCP server usage.
  • [probe] https://docs.warp.dev/openapi.jsonPROBE openapi: HTTP 200 at https://docs.warp.dev/openapi.json — contains "openapi" key
  • [probe] https://docs.warp.dev/reference/cliofficial CLI documented at https://docs.warp.dev/reference/cli

Export all of my data in open formats and leaveweight 3

3 (weight) × 3 (quality) × 0.6 (partial) = 5.4 of 30 max

  • [claimed-docs] https://www.warp.dev/blog/warp-is-now-open-sourcewe are shipping a (long-overdue) settings file so that users and agents get programmatic control over settings and easy portability between devices.
  • [claimed-docs] https://docs.warp.dev/privacy/privacyRead and audit Warp’s client source code at warpdotdev/warp, open source under AGPL v3
  • [claimed-docs] https://www.warp.dev/blog/warp-is-now-open-sourceWarp’s source code is now available at github.com/warpdotdev/warp with an AGPL license.

Read the product's source under an open licenseweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.warp.dev/privacy/privacyRead and audit Warp’s client source code at warpdotdev/warp, open source under AGPL v3
  • [claimed-docs] https://www.warp.dev/blog/warp-is-now-open-sourceWarp’s source code is now available at github.com/warpdotdev/warp with an AGPL license.
  • [claimed-docs] https://docs.warp.dev/privacy/privacyRead and audit Warp’s client source code at `warpdotdev/warp`, open source under AGPL v3

Self-host the core productweight 3

3 (weight) × 4 (quality) × 0.6 (partial) = 7.2 of 30 max

  • [claimed-docs] https://docs.warp.dev/privacy/privacyRead and audit Warp’s client source code at warpdotdev/warp, open source under AGPL v3
  • [claimed-docs] https://www.warp.dev/blog/warp-is-now-open-sourceWarp’s source code is now available at github.com/warpdotdev/warp with an AGPL license.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.
  • [community] https://hn.algolia.com/api/v1/items/42247583Warp co-founder: fair criticism, and this is the reason we removed the login requirement... the point of the login is that we have features that cost money to provide like AI and collaboration, not anything more nefarious.

Openness = 35.8 ÷ 100 × 100 = 35.8

Built-in AI83.3/100×0.15 of the PA blend

Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://www.warp.dev/warp-aiDescribe what you want to build and let Warp's built‑in agent handle the rest — writing code, running commands, and iterating until the task is done.
  • [claimed-docs] https://www.warp.dev/warp-aiConnect Warp AI to any tool via the Model Context Protocol. Pull context from databases, APIs, docs, and internal services so the AI understands your full stack.
  • [claimed-docs] https://www.warp.dev/warp-aiType '#' on your command line and start describing the command you want to run using natural language. Warp will load AI Command Suggestions as you type.
  • [claimed-docs] https://www.warp.dev/warp-aiRight‑click and 'Ask Warp AI' to explain any error in your command output.
  • [claimed-docs] https://docs.warp.devWrite and refactor code across your codebase * Debug issues and fix errors * Run commands and interpret results * Plan and execute multi-step tasks
  • [claimed-docs] https://docs.warp.dev/agents/generateGenerate (Legacy) turns natural language queries into precise terminal commands or contextual suggestions inside interactive CLI tools. Type `#` in the command line to describe what you want, and Warp generates the matching command in real time.
  • [claimed-docs] https://www.warp.dev/warp-aiRight‑click and 'Ask Warp AI' to explain any error in your command output. Warp AI can demystify opaque error messages and identify missing dependencies.

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.warp.devTriggers: React to events from Slack, Linear, GitHub, or custom webhooks
  • [claimed-docs] https://docs.warp.devSchedules: Run recurring tasks like dependency updates or dead code removal
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtopen the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review.
  • [claimed-docs] https://docs.warp.devObservability: Every run is tracked, auditable, and shareable with your team
  • [claimed-docs] https://docs.warp.dev/reference/cliThe Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe 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 agents locally or in the cloud, connect MCP servers, configure integrations, and authenticate without requiring the Warp desktop app.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/api--reference.txtAPI Keys - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
  • [claimed-docs] https://docs.warp.dev/reference/cliWith the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers like GitHub and Linear

Delegate tasks to a built-in AI assistant inside the productweight 3

3 (weight) × 9 (quality) × 1.0 (full) = 27.0 of 30 max

  • [claimed-docs] https://www.warp.dev/warp-aiDescribe what you want to build and let Warp's built‑in agent handle the rest — writing code, running commands, and iterating until the task is done.
  • [claimed-docs] https://www.warp.dev/warp-aiType '#' on your command line and start describing the command you want to run using natural language. Warp will load AI Command Suggestions as you type.
  • [claimed-docs] https://docs.warp.devWrite and refactor code across your codebase * Debug issues and fix errors * Run commands and interpret results * Plan and execute multi-step tasks
  • [claimed-docs] https://docs.warp.dev/agents/using-agentsBy default, if you ask an AI query immediately after interacting in Agent Mode, your query is sent as a **follow-up** to the current conversation.
  • [claimed-docs] https://docs.warp.dev/agents/using-agentsConversations are tied to sessions and you can run multiple Agent Mode conversations simultaneously in different windows, tabs, or panes.
  • [claimed-docs] https://www.warp.dev/warp-aiWarp supports Claude Sonnet and Opus, GPT, and Gemini Pro — and adds new models as they launch. Pick the model that fits your task, or let Warp route automatically.
  • [community] https://hn.algolia.com/api/v1/items/42247583Warp 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 generated commands at your fingertips.

Operate the product with natural-language commandsweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://www.warp.dev/warp-aiDescribe what you want to build and let Warp's built‑in agent handle the rest — writing code, running commands, and iterating until the task is done.
  • [claimed-docs] https://www.warp.dev/warp-aiType '#' on your command line and start describing the command you want to run using natural language. Warp will load AI Command Suggestions as you type.
  • [claimed-docs] https://www.warp.dev/warp-aiRight‑click and 'Ask Warp AI' to explain any error in your command output.
  • [claimed-docs] https://docs.warp.devWrite and refactor code across your codebase * Debug issues and fix errors * Run commands and interpret results * Plan and execute multi-step tasks
  • [claimed-docs] https://docs.warp.dev/agents/generateGenerate (Legacy) turns natural language queries into precise terminal commands or contextual suggestions inside interactive CLI tools. Type `#` in the command line to describe what you want, and Warp generates the matching command in real time.
  • [claimed-docs] https://docs.warp.devTerminal and Agent modes: Switch between a clean terminal for commands and a dedicated conversation view for multi-turn agent workflows.
  • [claimed-docs] https://docs.warp.dev/agents/using-agentsBy default, if you ask an AI query immediately after interacting in Agent Mode, your query is sent as a **follow-up** to the current conversation.

Built-in AI = 75.0 ÷ 90 × 100 = 83.3

Automation62.0/100×0.15 of the PA blend

Depth of automation primitives — rules, scheduling, bulk operations, webhooks.

Perform bulk operations across many items at onceweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://docs.warp.devParallelism: Run many agents concurrently across repos or tasks
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/factories.txtA software factory takes in requests (bug reports, feature specs, support escalations), and a coordinated fleet of agents works them into a stream of mergeable pull requests instead of a growing backlog.
  • [claimed-docs] https://docs.warp.devTriggers: React to events from Slack, Linear, GitHub, or custom webhooks
  • [claimed-docs] https://docs.warp.devSchedules: Run recurring tasks like dependency updates or dead code removal
  • [claimed-docs] https://docs.warp.dev/reference/cliThe Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.

Define rules that trigger actions automatically on eventsweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

  • [claimed-docs] https://docs.warp.devTriggers: React to events from Slack, Linear, GitHub, or custom webhooks
  • [claimed-docs] https://docs.warp.devSchedules: Run recurring tasks like dependency updates or dead code removal
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtopen the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review.
  • [claimed-docs] https://docs.warp.devObservability: Every run is tracked, auditable, and shareable with your team

Schedule recurring jobs or workflowsweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://docs.warp.devTriggers: React to events from Slack, Linear, GitHub, or custom webhooks
  • [claimed-docs] https://docs.warp.devSchedules: Run recurring tasks like dependency updates or dead code removal
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.
  • [claimed-docs] https://docs.warp.dev/reference/cliThe Oz CLI is the command-line tool for running and managing Warp’s cloud agents from any terminal, script, or CI pipeline.
  • [claimed-docs] https://docs.warp.dev/reference/cliWith the Oz CLI, you can: Run agents locally for development and debugging, Run agents on remote machines, Connect agents to MCP servers like GitHub and Linear

Version, review, and roll back my automationsweight 1

1 (weight) × 4 (quality) × 0.6 (partial) = 2.4 of 10 max

  • [claimed-docs] https://www.warp.dev/warp-aiWarp lets you save your most important workflows in Warp Drive so you can run them on‑demand or share with your team.
  • [claimed-docs] https://docs.warp.devObservability: Every run is tracked, auditable, and shareable with your team
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtopen the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review.
  • [claimed-docs] https://www.warp.dev/warp-aiWarp 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 hard part of naming, describing, and parameterizing the command.
  • [claimed-docs] https://docs.warp.dev/_llms-txt/automation-platform.txtCloud agents are autonomous, background agents that run on Warp’s cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub.

Automation = 49.6 ÷ 80 × 100 = 62.0