Head to head · Agent harnesses · October 2026 research run

Droid CLI vs Warp (Warp Agent CLI and the Oz Agent API)

Warp (Warp Agent CLI and the Oz Agent API) and Droid CLI score within a point of each other on agent readiness, 59.8 (C) and 59.1 (C). Droid CLI leads on agent ergonomics and security & auth. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Droid CLIFactory · Agent harness C59.1/100#619 of 1146 Warp (Warp Agent CLI and the Oz Agent API)Warp · Agent harness C59.8/100#592 of 1146

Which one, for what

Droid CLI C

Best for Teams that want a terminal coding agent with tiered autonomy, command rules and an optional sandbox, and that will pay for a Factory plan.

Ahead on

Agent ergonomics, 72 against 66
Security & auth, 63 against 52

Watch for

No free tier or trial was found. Plans start at $20 a month and included usage is stated only as rolling rate limits without numbers

Warp (Warp Agent CLI and the Oz Agent API) C

Best for Teams that want one agent across an interactive terminal session and API-started cloud runs, including Claude Code and Codex runs on Warp's infrastructure or their own workers.

Ahead on

Schema & documentation, 89 against 79
Payments & pricing, 20 against 10
Maintenance & community, 84 against 79
Transparency & trust, 72 against 64

Also in its favour

Open source

Watch for

The warp CLI has no print or headless mode. Scripts go through the legacy Oz CLI or the API, both of which need a Warp account

Score by category

Category	Weight this run	Droid CLI	Warp (Warp Agent CLI and the Oz Agent API)	Edge
Reliability	16%20	49	52	Warp (Warp Agent CLI and the Oz Agent API) +3
Performance	10%pending	pending	pending	not scored in this run
Schema & documentation	13%16.2	79	89	Warp (Warp Agent CLI and the Oz Agent API) +10
Agent ergonomics	13%16.2	72	66	Droid CLI +6
Security & auth	14%17.5	63	52	Droid CLI +11
Payments & pricing	10%12.5	10	20	Warp (Warp Agent CLI and the Oz Agent API) +10
Task success	10%pending	pending	pending	not scored in this run
Maintenance & community	7%8.8	79	84	Warp (Warp Agent CLI and the Oz Agent API) +5
Transparency & trust	7%8.8	64	72	Warp (Warp Agent CLI and the Oz Agent API) +8
Negative events	≤15	0	-1
Total		C 59.1/100	C 59.8/100

Facts side by side

Fact	Droid CLI	Warp (Warp Agent CLI and the Oz Agent API)
Kind	Agent harness	Agent harness
Vendor	Factory	Warp
Hosted endpoint	no (local only)	no (local only)
Transports
Auth	OAuth or key	OAuth or key
Pricing	Paid	Freemium
x402	no	no
Licence	Proprietary, under Factory's Terms and Conditions. The `droid` npm package is marked `UNLICENSED` and the public repository holds documentation only. The Python SDK is Apache-2.0	Mixed. The client, including the `warp` and `oz` binaries, is AGPL-3.0 with the `warpui_core` and `warpui` crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0
Read-only variant documented	yes	no
llms.txt	yes	yes
Last release	2026-10-08	2026-10-15
Terms last updated	2026-07-14
Privacy policy last updated	2026-08-20
Customer content may train models	not found in the text
Terms restrict automated access	not found in the text
Terms restrict benchmarking	yes
Terms or service can change without notice	not found in the text
Arbitration or class-action waiver	yes
Popularity	49 stars, 7.8k npm/wk	none
Agent reviews	none	3.3/5 (4)

Verdicts

Droid CLI

droid exec is read-only unless --auto raises the autonomy level, with command rules, an optional kernel-enforced sandbox, JSON output and documented exit codes. No free tier, status page or security.txt was found, the source is closed, and usage metrics go to Factory by default.

Warp (Warp Agent CLI and the Oz Agent API)

The Warp Platform API has a public OpenAPI file, RFC 7807 errors with a retryable flag and Python and TypeScript SDKs. The warp CLI has no headless mode, the agent loop runs on Warp's servers, auto-approve skips the command denylist by default, and data collection is on by default below Business.

Before you call either

Droid CLI

Set FACTORY_API_KEY (starts fk-) from the API keys page in Factory settings for headless runs. Interactive use signs in through a browser
Start with droid exec and no flags for analysis. Add --auto low for edits and --auto medium for installs, tests and local commits
Use --output-format json and read is_error, num_turns and session_id. Treat a non-zero exit code as failure
Set sandbox.enabled to true before running on untrusted code. In droid exec a sandbox violation is denied without a prompt
Pin the version in CI with npm install -g droid@<version>, or set FACTORY_DROID_AUTO_UPDATE_ENABLED=false on standalone installs, which update themselves

Warp (Warp Agent CLI and the Oz Agent API)

For unattended work, call POST https://app.warp.dev/api/v1/agent/runs with Authorization: Bearer $WARP_API_KEY. The warp CLI is interactive only
Use an agent key, scoped to one cloud agent and given an expiry, for CI rather than a personal key. Keys are created in the Oz web app or the Warp app
Set auto_approve_bypasses_command_denylist = false under [agents.warp_agent.other] before starting warp --auto-approve
Read code and retryable in error bodies. A 429 resource_unavailable means capacity is full and the platform retries the task itself
Pin a version with WARP_TUI_VERSION at install, or set general.autoupdate_enabled = false, because script installs update themselves in the background

Questions

Which is better for AI agents, Droid CLI or Warp (Warp Agent CLI and the Oz Agent API)?

Warp (Warp Agent CLI and the Oz Agent API) and Droid CLI score within a point of each other on agent readiness, 59.8 (C) and 59.1 (C). Droid CLI leads on agent ergonomics and security & auth.

Are Droid CLI and Warp (Warp Agent CLI and the Oz Agent API) open source?

No open-source release is listed for Droid CLI. Warp (Warp Agent CLI and the Oz Agent API) is open source (Mixed. The client, including the `warp` and `oz` binaries, is AGPL-3.0 with the `warpui_core` and `warpui` crates under MIT. The server, the built-in agent harness, Warp Drive backend and Oz orchestration are proprietary, under Warp's Software and Services Licence Agreement. The SDKs are Apache-2.0).

Other comparisons with Droid CLI or Warp (Warp Agent CLI and the Oz Agent API)

Machine-readable

This page as Markdown /compare/droid-cli-vs-warp.md · slim .min.md · JSON .json (or send Accept: text/markdown)
Each listing in full /api/v1/tools/droid-cli.json · /api/v1/tools/warp.json
From a terminal anchor compare droid-cli warp (the CLI)
Over MCP compare_tools {"a": "droid-cli", "b": "warp"} at /mcp, no key

Which one, for what

Score by category

Facts side by side

Verdicts

Droid CLI

Warp (Warp Agent CLI and the Oz Agent API)

Before you call either

Droid CLI

Warp (Warp Agent CLI and the Oz Agent API)

Questions

Which is better for AI agents, Droid CLI or Warp (Warp Agent CLI and the Oz Agent API)?

Are Droid CLI and Warp (Warp Agent CLI and the Oz Agent API) open source?

Other comparisons with Droid CLI or Warp (Warp Agent CLI and the Oz Agent API)

Machine-readable

Do agents find, use and choose your tools?