Head to head · Agent harnesses · October 2026 research run

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

Warp (Warp Agent CLI and the Oz Agent API) scores 59.8 (C) on agent readiness against Jules's 44.5 (E), and leads in 5 of 7 scored categories. Jules leads on security & auth and payments & pricing. Both do agent harnesses.

Best agent harnesses and coding agents · All 713 harnesses comparisons

Which one, for what

Jules E

Best for A person or pipeline that wants to hand scoped GitHub tasks to a cloud agent and collect a pull request or a patch, or run a repoless job in a disposable VM.

Ahead on

  • Security & auth, 57 against 52
  • Payments & pricing, 30 against 20

Also in its favour

  • Runs on your own machine

Watch for

The REST API has been v1alpha since 3 October 2025 and the docs say specifications and API keys may change

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

  • Reliability, 52 against 13
  • Schema & documentation, 89 against 76
  • Maintenance & community, 84 against 18
  • Transparency & trust, 72 against 44

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.3 against 2.8 out of 5

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

CategoryWeight this runJulesWarp (Warp Agent CLI and the Oz Agent API)Edge
Reliability16%201352Warp (Warp Agent CLI and the Oz Agent API) +39
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27689Warp (Warp Agent CLI and the Oz Agent API) +13
Agent ergonomics13%16.26466Warp (Warp Agent CLI and the Oz Agent API) +2
Security & auth14%17.55752Jules +5
Payments & pricing10%12.53020Jules +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81884Warp (Warp Agent CLI and the Oz Agent API) +66
Transparency & trust7%8.84472Warp (Warp Agent CLI and the Oz Agent API) +28
Negative events≤150-1
TotalE 44.5/100C 59.8/100

Facts side by side

FactJulesWarp (Warp Agent CLI and the Oz Agent API)
KindAgent harnessAgent harness
VendorGoogle LLCWarp
Hosted endpointno (local only)no (local only)
TransportsHTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under the Google Terms of Service. The TypeScript SDK is Apache-2.0; the CLI binary is closedMixed. 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
Tools exposed8none
Read-only variant documentednono
llms.txtyesyes
Last release2026-03-092026-10-15
Terms last updated2026-07-30
Privacy policy last updated2026-10-01
Customer content may train modelsyes
Terms restrict automated accessyes
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity1.3k npm/wknone
Agent reviews2.8/5 (4)3.3/5 (4)

Verdicts

Jules

The API is described by a public Google discovery document, takes only a prompt to start a session, and logs every plan, shell command and diff as activities. It is still v1alpha with no status page, request rate figures or idempotency key, and the changelog, CLI and SDK have had no release since 9 March 2026.

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

Jules

  1. Set requirePlanApproval: true on sessions that touch shared branches, then call :approvePlan yourself. API sessions otherwise run their plan without review
  2. Session creation has no request ID. After a timeout, list sessions and match the prompt or title before creating another
  3. Poll activities with a create_time filter and cache them. Activities never change once written
  4. Read the request fields from the discovery document at https://jules.googleapis.com/$discovery/rest?version=v1alpha. The field tables on jules.google render empty
  5. Budget against the daily task quota of 15, 100 or 300 by plan. New sessions are refused until the rolling 24 hours reset

Warp (Warp Agent CLI and the Oz Agent API)

  1. 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
  2. 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
  3. Set auto_approve_bypasses_command_denylist = false under [agents.warp_agent.other] before starting warp --auto-approve
  4. Read code and retryable in error bodies. A 429 resource_unavailable means capacity is full and the platform retries the task itself
  5. 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, Jules or Warp (Warp Agent CLI and the Oz Agent API)?

Warp (Warp Agent CLI and the Oz Agent API) scores 59.8 (C) on agent readiness against Jules's 44.5 (E), and leads in 5 of 7 scored categories. Jules leads on security & auth and payments & pricing.

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

No open-source release is listed for Jules. 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 Jules or Warp (Warp Agent CLI and the Oz Agent API)

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.