Warp
Terminal and AI agent workspace for coding tasks, local command execution and cloud agent workflows.
Score calculation
(4 + 6 + 7 + 1 + 7) ÷ 5 = 5.0
5 of six dimensions rated. Unrated dimensions are excluded from the average.
Full scoring method ↗Setup details
Warp terminal and Warp Agent. Commands run locally, while prompts and selected context may reach Warp and model providers; cloud Automation Platform is another execution route.
What fits your needs
Warp terminal and Warp Agent. Commands run locally, while prompts and selected context may reach Warp and model providers; cloud Automation Platform is another execution route.
Use Warp Agent or another CLI
Warp supports its own agent and third-party terminal coding agents.
See the evidence
Choose model/profile
Agent profiles can set model and autonomy.
See the evidence
Tradeoffs to expect
Separate data controls
Warp telemetry and model provider retention are controlled separately.
Cloud automation
Factories run agents on Warp’s Automation Platform.
See the evidence
How to switch
Use BYOK where eligible
Connect an eligible OpenAI, Anthropic or Google key; Warp remains in the request path.
Practical questions
Review Help Improve Warp
Check account privacy settings and plan before sending AI interaction data.
Check model fallbacks
Warp may use a fallback if the chosen model becomes unavailable.
See the evidence
Warp documents model selection and agent profiles but no energy measurements.
See the evidence
Model and profile controls provide route choices without a measured resource outcome.
1 + 1 reporting + 0 electricity + 2 controls = 4/10. This grades documented practices and transparency.
Task energy, water and facility-level electricity are unknown.
- Reporting1/3
- Agent and provider routes are documented, without an energy footprint.
- Electricity sourcing0/3
- No electricity sourcing or attributable footprint is reported.
- Resource controls2/3
- Model and agent profiles are configurable without measured energy savings.
Water disclosure
Water reporting has not been assessed for this choice.
Warp supports multiple model providers and BYOK, so no single training dataset applies.
See the evidence
Select the exact model and provider route before assigning training-data rights.
Warp documents hosted model choice and BYOK. Those settings change routing and billing but don’t settle permission for underlying training data.
The selected model/version and provider define the training data and terms.
Warp’s provider agreements prohibit provider training under supported ZDR routes, while Warp telemetry can collect AI interactions on personal plans.
See the evidence
Warp says model providers under ZDR do not train on customer data. Its own telemetry settings may collect AI interactions and console input when Help Improve Warp is enabled; Business and Enterprise have organization-wide ZDR.
Check plan, telemetry settings, selected model exceptions and cloud automation route; provider ZDR does not mean no Warp telemetry.
Warp is an open-source terminal client with hosted AI services and third-party CLI agent integrations.
See the evidence
Warp documents client source availability under AGPL v3, model choice and third-party agent support. Hosted AI and cloud orchestration remain separate managed services.
External providers and cloud agents have separate terms and data paths.
Warp has no workforce disclosures covering the AI supply chain in the reviewed public sources.
See the evidence
The reviewed public sources do not describe employee conditions, worker voice, or contractor protections for Warp. Missing disclosure is an evidence gap, not proof of mistreatment.
1 + 0 + 0 + 0 = 1/10. Documented worker protections; missing disclosure is an evidence gap.
Contractor conditions, data annotation and moderation, worker representation, remedies and independent review remain unknown.
- Pay & conditions0/3
- No worker conditions policy or implementation evidence was found in reviewed sources.
- Worker voice & remedy0/3
- No worker voice, representation or grievance safeguard was found in reviewed sources.
- Evidence & follow-through0/3
- No independent worker-level evidence was found in reviewed sources.
No military relationship was established from the reviewed public sources for Warp; the score reflects uncertainty.
See the evidence
The sources reviewed did not establish a military contract or operational defense offering for Warp. The method starts at 7 when a military relationship is not established; missing disclosure is not proof that none exists.
7 base + 0 safeguard adjustment = 7/10 (0 of 9 safeguard points; every 3 adds 1). No military relationship was established in the cited sources. This ranks above known defense ties without claiming a verified clean record.
This bounded review cannot rule out unreported customers, indirect use, subcontracting or future work.
- Use restrictions0/4
- No public military-use restriction was found in the reviewed sources.
- Enforcement & oversight0/3
- No independently evidenced military-use oversight was found.
- Relationship disclosure0/2
- No military customer or relationship disclosure was identified.
No military relationship for Warp was established in the reviewed sources; this is not proof that none exists.
Military rubric ↗Warp was not named on the two BNC campaign pages checked. This limited list check is not an endorsement.
See the evidence
The BNC selects specific company targets; Warp was not named in the official priority guide or No Tech campaign when checked. This is not a nationality-based assessment or proof that the company has no other relevant relationships.
This covers only the BNC corporate guide and No Tech page. Other BDS campaigns, local calls, ownership changes, contractors and business relationships are outside the check.