---
title: "Warp — The Open Platform for Automating Development"
url: https://stacklist.com/card/7da499a7-877f-4398-9bd9-975d4076dd5e
source_url: "https://www.warp.dev/"
stack: https://stacklist.com/stack/b1d3670b-d431-4e1c-b4ad-6bd64dd146f9
summary: "Warp is an open infrastructure platform for cloud software factories that automates the entire SDLC through factories-as-code, AI agents, and integrations with GitHub and other tools. It provides API, CLI, SDK, and MCP interfaces with built-in evals, self-improvement capabilities, and multi-surface monitoring for enterprise-scale deployment."
tags: "warp, sdlc, cloud-software, factories-as-code, ai-agents, devops, automation"
key_entities: "Warp (technology), Claude-5-Fable-High (technology), GitHub (technology), MCP (technology), Factories as Code (concept), SDLC (concept), Acme (organization), GLM-5.2-Fireworks (technology)"
classification: "reference"
content_hash: "sha256:a97b9eddad7651ba414bf418ea2a2f68070e47bade98609374e39af5b0963224"
acp_version: "0.2"
token_counts_approximate: 2408
visibility: public
agent_accessible: true
status: "final"
---

# Warp — The Open Platform for Automating Development

[S] SDLC [Q] Quality loop [E] Enterprise [L] Layers [G] Governance [W] Warp everywhere [F] FAQ request early access Open infrastructure for cloud software factories build on Warp: factories as code, any model or harness, with evals, benchmarks, and self-improvement built in. request early access download warp terminal get up to $10,000 in free factory usage &gt;_ [ fig. 1 — the factory ] ⌗ live factory.yaml factory.yaml applied to all 112 agents # factory.yaml schemaVersion: v1alpha1 name: acme-web repositories: - owner: acme name: web mcpServers: github: warpId: mcp_github agentDefaults: model: claude-5-fable-high trusted by 800k+ devs at SDLC coverage Beyond CI/CD to automating the whole SDLC defined in code, built for scale, and easy to deploy. 01 opinionated, but flexible set up your first factory in 5 minutes, build it out over time. &gt;_ [ fig. 2 · quickstart ] ⌗ 02 factories as code repos, agents, models, permissions, and checkpoints in one definition. &gt;_ [ fig. 2 · factory.yaml ] ⌗ # factory.yaml — factories as code schemaVersion: v1alpha1 name: pr-review repositories: - owner: acme name: web agentDefaults: model: claude-5-fable-high # agents/foreman/agent.md agentType: FOREMAN # agents/review/agent.md agentType: REVIEW model: glm-5.2-fireworks # automations/on-pr/automation.md agent: review triggers: - provider: github event: pull_request_ready 03 API, CLI, SDK and MCP built as a platform, not a vertical product or AI teammate. &gt;_ [ fig. 2 · API / CLI / SDK / MCP ] ⌗ # cli $ warp agent run-cloud --environment ENV_ID \ --prompt &quot;fix LIN-482, low risk only&quot; # api $ curl -X POST https://app.warp.dev/api/v1/agent/runs \ -H &quot;Authorization: Bearer $WARP_API_KEY&quot; \ -H &quot;Content-Type: application/json&quot; \ -d &#x27;{ &quot;prompt&quot;: &quot;fix LIN-482&quot; }&#x27; { &quot;run_id&quot;: &quot;run_4026&quot; , &quot;state&quot;: &quot;QUEUED&quot; } # sdk (typescript) const run = await client.agent.run({ prompt: &#x27;fix LIN-482&#x27; }); console.log(run.run_id); # mcp · warp-factory server { &quot;tool&quot; : &quot;send_task&quot; , &quot;factory_uid&quot; : &quot;fct_acme_web&quot; , &quot;title&quot; : &quot;Fix LIN-482&quot; , &quot;note&quot; : &quot;low risk only&quot; } 04 integrations work flows in from chat, tickets, and source control; status flows back to where it started. &gt;_ [ fig. 2 · integrations ] ⌗ 05 any surface watch, steer, and hand off runs from web, mobile, terminal, or IDE. &gt;_ [ fig. 2 · any surface ] ⌗ 06 evals, self-improvement, and memory every run is scored; observer agents open PRs against your factory config to improve it. &gt;_ [ fig. 2 · self-improvement ] ⌗ &gt;_ [ fig. 2 · quickstart ] ⌗ &gt;_ [ fig. 2 · factory.yaml ] ⌗ # factory.yaml — factories as code schemaVersion: v1alpha1 name: pr-review repositories: - owner: acme name: web agentDefaults: model: claude-5-fable-high # agents/foreman/agent.md agentType: FOREMAN # agents/review/agent.md agentType: REVIEW model: glm-5.2-fireworks # automations/on-pr/automation.md agent: review triggers: - provider: github event: pull_request_ready &gt;_ [ fig. 2 · API / CLI / SDK / MCP ] ⌗ # cli $ warp agent run-cloud --environment ENV_ID \ --prompt &quot;fix LIN-482, low risk only&quot; # api $ curl -X POST https://app.warp.dev/api/v1/agent/runs \ -H &quot;Authorization: Bearer $WARP_API_KEY&quot; \ -H &quot;Content-Type: application/json&quot; \ -d &#x27;{ &quot;prompt&quot;: &quot;fix LIN-482&quot; }&#x27; { &quot;run_id&quot;: &quot;run_4026&quot; , &quot;state&quot;: &quot;QUEUED&quot; } # sdk (typescript) const run = await client.agent.run({ prompt: &#x27;fix LIN-482&#x27; }); console.log(run.run_id); # mcp · warp-factory server { &quot;tool&quot; : &quot;send_task&quot; , &quot;factory_uid&quot; : &quot;fct_acme_web&quot; , &quot;title&quot; : &quot;Fix LIN-482&quot; , &quot;note&quot; : &quot;low risk only&quot; } &gt;_ [ fig. 2 · integrations ] ⌗ &gt;_ [ fig. 2 · any surface ] ⌗ &gt;_ [ fig. 2 · self-improvement ] ⌗ quality loop Baked-in measurement and self-improvement evals, benchmarks, and self-improvement loops drive measurable gains. &gt;_ [ fig. 4 · quality loop · sample run ] ⌗ evals on your own work pass 96% 100% 50% 0% apr 01 may 01 jun 01 jul 01 8/13 07:03 fail 0.4 $0.39 8/13 07:02 pass 0.8 $0.53 8/13 07:02 pass 0.8 $0.46 benchmarks across models best 1.00x 1.0x 0.5x 0x apr 01 may 01 jun 01 jul 01 Claude Fable 5 pass 1.00x $0.53 GPT-5.6 Sol pass 0.94x $0.41 Gemini 3.6 Flash fail 0.89x $0.32 self-improvement loops auto-fix +3.7 +4 +2 0 apr 01 may 01 jun 01 jul 01 memory updated pass +0.2 #4021 prompts tuned pass +3.2% #4022 regression caught fail -0.4 #4023 case study Cutting our cost per PR from $80 to $30 How we used Warp Factories Benchmarks to test models on our own engineering tasks and optimize for cost without sacrificing quality. read case study Warp is enterprise ready Run agents confidently with guardrails in place, centrally configured agent access, and centrally managed permissions. Rectangle Health uses Warp to build a self-improving AI teammate Rectangle Health turned a senior engineer&#x27;s side project into Rex, a self-improving AI teammate built on Oz that now writes 54% of its own code. read the story Docker uses Warp to reduce onboarding time and give every engineer a shared source of truth Docker adopted Warp for a more user-friendly terminal experience, using Warp Drive to streamline repetitive workflows and boost team productivity. read the story no lock-in Open at every layer &gt;_ [ fig. 3 · open at every layer ] ⌗ layer 01 Any agent warp claude code codex cursor any MCP-capable coding agent. layer 02 Any model frontier open-weight frontier or open-weight, chosen per pipeline stage. layer 03 Your compute or ours warp cloud self-hosted warp&#x27;s cloud, or self-hosted in your own VPC. layer 04 Data lives where you want pluggable zero-retention your VPC you own and store what your factory produces. governance Control your coding agent chaos continuous improvement, better governance and security, by default. &gt;_ [ fig. 5 · control plane ] ⌗ increase agent roi · cost per pr $— compute platform inference one control plane for every agent resolve merge conflicts on server pr 14090 fable 5 orchestration f now refactor auth middleware for session reuse opus 4.8 claude code z 14m investigate child process kill issue fable 5 slack j 37m investigate usize panic in offset code gpt-5.6 sol slack f 1h fix desktop tab crash gemini 3.6 slack j 2h add rate limiting to public api endpoints gpt-5.3 codex e 4h agents prove their work with computer use every factory agent captures a screenshot or video so you can verify its work before shipping a PR. f Activations dropped on the contact sales page this week. Can you investigate and fix the culprit? On it — opening the browser to test the flow myself . . . warp.dev/contact-sales Bring Warp to your team Enter your work email and answer one question — we&#x27;ll get you to the right person on our team. Book a demo Work Email* you@company.com CONTINUE Trusted by over 800,000 developers and thousands of engineering teams at leading companies Found it — the testimonials section was hidden by collapsing divs. Patched, PR #436 is up for review. Use Warp everywhere Warp is an open agentic development platform that was built to work wherever and however you work. Factories A software factory that automates and orchestrates software development. request access Terminal An open-source terminal built for AI-assisted software development. Download Warp Agent CLI A powerful coding agent that works in any terminal. $ curl -fsSL https://app.warp.dev/download/agent-cli | bash Mac | Linux | Windows Frequently asked questions what is a cloud software factory? [+] a factory is a fleet of agents wired to your SDLC — triggered by an issue, a slack message, or a schedule, and coordinated by warp factories from triage through review to a mergeable PR. how do i define a factory? [+] as code, in a factory.yaml + supporting agent files. define triggers, agents, models, and approval gates — check it into your repo like any other config. do i have to use warp&#x27;s models or config? [+] no. bring your own model or harness (e.g. claude code or codex) — warp factories works with whatever your team prefers and helps identify the most cost-effective configuration over time. do i need warp terminal to use factories? [+] no. factories is a separate product — nobody at your company has to use warp terminal. work comes in through tools you already use, like slack, linear, jira, github, and gitlab. if you do use warp terminal, it has built-in factory integrations (native mcp) so you can iterate locally. how much of my SDLC can be automated? [+] most orgs start around 20-30% of PRs fully automated, starting with simple tasks. over time this goes up as models improve and your factory self-improves. where does our data live? [+] wherever you choose — warp&#x27;s cloud, or fully self-hosted inside your own VPC, under your existing retention and compliance rules. how do humans interact with the factory? [+] humans put work into the factory via your existing tools like slack, teams, linear, jira, github and gitlab. at any time you can iterate on that work locally and the factory agents loop you in proactively when they need help. can we start small? [+] yes — most teams start with a single low-risk workflow, like dependency bumps or flaky test triage, before expanding coverage. what does it cost? [+] usage-based, priced per agent run. qualifying orgs get $10k of factory usage during closed early access.
