podium

Warp Factories / Oz

48 of 51 criteria have a sourced finding; 45 were also cross-checked by a second agent. Every comparison that includes Warp Factories / Oz links here for scope, limitations, atomic answers and sources.

Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.

Rubric
0.3 · 51 criteria
Source checks
2026-11-07
Agent cross-checked
45 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Agent cross-checked partial

Warp desktop app is offered on macOS, Windows and Linux and exposes the cloud-agent setup and conversation surface documented by its quickstart. Warp Factories is the current branded web offering for factory-based team development workflows. Existing standalone cloud runs continue in the Oz web app; the current transition guide keeps Oz web, CLI, SDK and API paths distinct from new Factories. These sources establish current branding and retained Oz surfaces, not an explicit blanket Oz rename or shutdown. The Oz web app works on mobile devices and manages runs, schedules, environments and integrations without installing Warp. The oz CLI starts cloud runs and unmanaged current-host agents and manages environments, schedules and run history. Browser users create runs, inspect transcripts and outputs, edit saved agents and pause schedules.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app, Warp desktop cloud-agent client · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: mobile_apps, editor_extensions, notifications, cross_device_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
  • No explicit statement that every Oz product/workflow was renamed Warp Factories was established. Standalone Oz tooling/web paths remain documented. October 3 transition-toward-GA wording is not an exact GA launch; current docs/page retain early-access wording.
9 atomic answers
  • Desktop os [supported] Warp desktop app is offered on macOS, Windows and Linux and exposes the cloud-agent setup and conversation surface documented by its quickstart. Sources: warp-oz:gap07-desktop, warp-oz:gap07-desktop-cloud.
  • Mobile apps [unknown] Not established for mobile apps in the named first-party source pass. Product access and scenario tests were not run.
  • Browser [supported] Warp Factories is the current branded web offering for factory-based team development workflows. Existing standalone cloud runs continue in the Oz web app; the current transition guide keeps Oz web, CLI, SDK and API paths distinct from new Factories. These sources establish current branding and retained Oz surfaces, not an explicit blanket Oz rename or shutdown. Sources: warp-oz:nov07-platform, warp-oz:gap07-factory-name, warp-oz:gap07-oz-transition, warp-oz:gap07-factory-offsite, warp-oz:gap07-oz-name.
  • Mobile browser [supported] The Oz web app works on mobile devices and manages runs, schedules, environments and integrations without installing Warp. Sources: warp-oz:gap07-web.
  • Cli [supported] The oz CLI starts cloud runs and unmanaged current-host agents and manages environments, schedules and run history. Sources: warp-oz:gap07-cli.
  • Editor extensions [unknown] Not established for editor extensions in the named first-party source pass. Product access and scenario tests were not run.
  • Task actions [supported] Browser users create runs, inspect transcripts and outputs, edit saved agents and pause schedules. Sources: warp-oz:gap07-web.
  • Notifications [unknown] Not established for notifications in the named first-party source pass. Product access and scenario tests were not run.
  • Cross device continuity [unknown] Not established for cross device continuity in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-platform, warp-oz:gap07-web, warp-oz:gap07-cli, warp-oz:gap07-desktop, warp-oz:gap07-desktop-cloud, warp-oz:gap07-factory-name, warp-oz:gap07-oz-transition, warp-oz:gap07-factory-offsite, warp-oz:gap07-oz-name

Agent cross-checked partial

The documented harness identifiers are oz, claude and codex; factory agents can use different harnesses. Claude Code cloud auth supports Anthropic or Anthropic Bedrock credentials; Codex uses OpenAI API keys. Harness selection is configured per factory agent or standalone run through app, web, API or SDK. Orchestrations can mix Warp Agent, Claude Code and Codex with a harness-agnostic messaging bus.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: custom_adapters. No configured product fixture was run; documentation does not establish successful hands-on behavior.
5 atomic answers
  • Harnesses [supported] The documented harness identifiers are oz, claude and codex; factory agents can use different harnesses. Sources: warp-oz:nov07-harnesses.
  • Model providers [supported] Claude Code cloud auth supports Anthropic or Anthropic Bedrock credentials; Codex uses OpenAI API keys. Sources: warp-oz:gap07-auth.
  • Custom adapters [unknown] Not established for custom adapters in the named first-party source pass. Product access and scenario tests were not run.
  • Session integration [supported] Harness selection is configured per factory agent or standalone run through app, web, API or SDK. Sources: warp-oz:nov07-harnesses.
  • Mixed harness operation [supported] Orchestrations can mix Warp Agent, Claude Code and Codex with a harness-agnostic messaging bus. Sources: warp-oz:gap07-orchestration.

Sources: warp-oz:nov07-harnesses, warp-oz:gap07-auth, warp-oz:gap07-orchestration

Agent cross-checked partial

Managed-secret Codex cloud authentication bills a funded OpenAI API account, not a ChatGPT subscription; Claude Code managed-secret setup similarly documents provider API keys. Customer-supplied inference includes BYOK and custom endpoints; organizations over ten employees require Business or Enterprise for these routes. Harness auth secrets can be team or personal for standalone runs; factory agents require team secrets. Warp authentication and authorization are required in addition to the selected provider credential. Factory agents can select compatible team-owned secrets; local CLI subscription sign-in is a separate path.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-21 inherited-lead additions: docs.warp.dev Platform usage, Harnesses, Factories, Factory dashboard and Factory Home pages (read 2026-11-21) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
  • Unknown after the 2026-11-21 inherited-lead recheck of first-party docs, releases and public code: local_models. No configured product fixture was run; documentation does not establish successful hands-on behavior.
7 atomic answers
  • Agent subscriptions [unsupported] Managed-secret Codex cloud authentication bills a funded OpenAI API account, not a ChatGPT subscription; Claude Code managed-secret setup similarly documents provider API keys. Sources: warp-oz:gap07-auth.
  • Api accounts [supported] Customer-supplied inference includes BYOK and custom endpoints; organizations over ten employees require Business or Enterprise for these routes. Sources: warp-oz:nov07-platform-billing.
  • Vendor credits [partial] Warp-provided inference, hosted compute and platform activity draw from usage funding; customer-supplied inference is billed by its provider. The $3/AH rate applies to dollar-billed Terminal/local-agent Free, Build, Max and Business accounts. Factory runs on Start, Scale and Enterprise use shared team/workspace funding, with no Factory rate stated on the checked page. Sources: warp-oz:ade158-platform-usage, warp-oz:b07-harnesses.
  • Local models [unknown] Not established for local models in the named first-party source pass. Product access and scenario tests were not run.
  • Account switching [supported] Harness auth secrets can be team or personal for standalone runs; factory agents require team secrets. Sources: warp-oz:gap07-auth.
  • Vendor account requirement [supported] Warp authentication and authorization are required in addition to the selected provider credential. Sources: warp-oz:gap07-auth.
  • Provider restrictions [supported] Factory agents can select compatible team-owned secrets; local CLI subscription sign-in is a separate path. Sources: warp-oz:gap07-auth.

Sources: warp-oz:nov07-platform-billing, warp-oz:nov07-harnesses, warp-oz:gap07-auth, warp-oz:b07-platform-usage, warp-oz:b07-harnesses, warp-oz:ade158-platform-usage

Agent cross-checked partial

Guided browser onboarding offers automation, app-based cloud agents or programmatic agent workflows. Schedules without an environment can run in a bare sandbox without repository access. Standalone environments clone authorized GitHub repositories. The guide names repository authorization and a public glibc Docker image. Web, CLI and /create-environment configure repos, image and setup commands. Install Oz CLI on the execution host, set a Warp API key and invoke oz agent run in the desired directory.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: local_git_without_remote. No configured product fixture was run; documentation does not establish successful hands-on behavior.
7 atomic answers
  • First task setup [supported] Guided browser onboarding offers automation, app-based cloud agents or programmatic agent workflows. Sources: warp-oz:gap07-web.
  • No git [supported] Schedules without an environment can run in a bare sandbox without repository access. Sources: warp-oz:gap07-schedule-details.
  • Local git without remote [unknown] Not established for local git without remote in the named first-party source pass. Product access and scenario tests were not run.
  • Hosted git [supported] Standalone environments clone authorized GitHub repositories. Sources: warp-oz:gap07-environment.
  • Prerequisite guidance [supported] The guide names repository authorization and a public glibc Docker image. Sources: warp-oz:gap07-environment.
  • Managed cloud setup [supported] Web, CLI and /create-environment configure repos, image and setup commands. Sources: warp-oz:gap07-environment.
  • Byo vps onboarding [supported] Install Oz CLI on the execution host, set a Warp API key and invoke oz agent run in the desired directory. Sources: warp-oz:gap07-unmanaged.

Sources: warp-oz:gap07-web, warp-oz:gap07-environment, warp-oz:gap07-unmanaged, warp-oz:gap07-schedule-details

Agent cross-checked partial

oz agent run-cloud and oz agent run provide distinct managed and unmanaged execution. Agent/run endpoints submit work and retrieve status, transcripts and results; factory endpoints are a separate route. The page lists API and SDK access for standalone runs. Hosted Factory MCP at app.warp.dev/api/v1/mcp/factory exposes task dispatch, lookup, conversation, handoff and configuration. CLI manages runs, schedules, environments, secrets, MCP configuration and saved agent settings. Factory MCP uses browser OAuth or agent bearer API key; there is no read-only/per-factory scope.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: webhooks, stability. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Cli [supported] oz agent run-cloud and oz agent run provide distinct managed and unmanaged execution. Sources: warp-oz:gap07-cli.
  • Api [supported] Agent/run endpoints submit work and retrieve status, transcripts and results; factory endpoints are a separate route. Sources: warp-oz:nov07-platform.
  • Sdk [supported] The page lists API and SDK access for standalone runs. Sources: warp-oz:nov07-platform.
  • Mcp server [supported] Hosted Factory MCP at app.warp.dev/api/v1/mcp/factory exposes task dispatch, lookup, conversation, handoff and configuration. Sources: warp-oz:gap07-factory-mcp.
  • Webhooks [unknown] Not established for webhooks in the named first-party source pass. Product access and scenario tests were not run.
  • Operations [supported] CLI manages runs, schedules, environments, secrets, MCP configuration and saved agent settings. Sources: warp-oz:gap07-cli.
  • Authentication [supported] Factory MCP uses browser OAuth or agent bearer API key; there is no read-only/per-factory scope. Sources: warp-oz:gap07-factory-mcp.
  • Stability [unknown] Not established for stability in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-platform, warp-oz:gap07-cli, warp-oz:gap07-factory-mcp

Agent cross-checked partial

Factory and standalone agents use stdio, Streamable HTTP or SSE MCP servers. MCP exposes internal tools, external APIs and local processes. Factory-wide MCP grants apply to all agents or can be scoped per agent. The factory definition or standalone config declares connections; connected integrations add separately authorized tools.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: plugins, instructions_import, authentication. No configured product fixture was run; documentation does not establish successful hands-on behavior.
7 atomic answers
  • Mcp client [supported] Factory and standalone agents use stdio, Streamable HTTP or SSE MCP servers. Sources: warp-oz:gap07-mcp.
  • Plugins [unknown] Not established for plugins in the named first-party source pass. Product access and scenario tests were not run.
  • Custom tools [supported] MCP exposes internal tools, external APIs and local processes. Sources: warp-oz:gap07-mcp.
  • Instructions import [unknown] Not established for instructions import in the named first-party source pass. Product access and scenario tests were not run.
  • Authentication [unknown] Not established for authentication in the named first-party source pass. Product access and scenario tests were not run.
  • Permission scope [supported] Factory-wide MCP grants apply to all agents or can be scoped per agent. Sources: warp-oz:gap07-mcp.
  • Integration owner [supported] The factory definition or standalone config declares connections; connected integrations add separately authorized tools. Sources: warp-oz:gap07-mcp.

Sources: warp-oz:gap07-mcp

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Planning and context

Agent cross-checked partial

A direct request goes to the factory foreman. Connected integrations and automations ingest issues, support requests and pull requests. Integration or API requests can start cloud tasks with issue descriptions or PR diffs as context. A work item keeps its identity across stages and contributing agents. The foreman returns work for revisions and continues existing agent conversations.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: local_creation, authoritative_tracker, sync, external_roundtrips. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Local creation [unknown] Not established for local creation in the named first-party source pass. Product access and scenario tests were not run.
  • Prompt intake [supported] A direct request goes to the factory foreman. Sources: warp-oz:gap07-factory-flow.
  • External import [supported] Connected integrations and automations ingest issues, support requests and pull requests. Sources: warp-oz:gap07-factory-flow.
  • Chat git triggers [supported] Integration or API requests can start cloud tasks with issue descriptions or PR diffs as context. Sources: warp-oz:nov07-platform.
  • Authoritative tracker [unknown] Not established for authoritative tracker in the named first-party source pass. Product access and scenario tests were not run.
  • Stable ids [supported] A work item keeps its identity across stages and contributing agents. Sources: warp-oz:gap07-factory-flow.
  • Sync [unknown] Not established for sync in the named first-party source pass. Product access and scenario tests were not run.
  • Supported edits [supported] The foreman returns work for revisions and continues existing agent conversations. Sources: warp-oz:gap07-factory-flow.
  • External roundtrips [unknown] Not established for external roundtrips in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-platform, warp-oz:gap07-factory-flow

Agent cross-checked partial

A spec agent defines behavior, constraints and validation criteria when planning is needed. Spec planning includes product behavior and validation criteria. The implement agent uses the planned work to create a branch and pull request. Work can return to earlier agents for revisions while retaining the work item context.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: editors, revisions, restart_persistence. No configured product fixture was run; documentation does not establish successful hands-on behavior.
7 atomic answers
  • Plans [supported] A spec agent defines behavior, constraints and validation criteria when planning is needed. Sources: warp-oz:gap07-factory-flow.
  • Acceptance criteria [supported] Spec planning includes product behavior and validation criteria. Sources: warp-oz:gap07-factory-flow.
  • Editors [unknown] Not established for editors in the named first-party source pass. Product access and scenario tests were not run.
  • Revisions [unknown] Not established for revisions in the named first-party source pass. Product access and scenario tests were not run.
  • Amendment [supported] Work can return to earlier agents for revisions while retaining the work item context. Sources: warp-oz:gap07-factory-flow.
  • Restart persistence [unknown] Not established for restart persistence in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-factory-flow

Agent cross-checked partial

Default spec approval is foreman instruction policy; merging is enforced by repository permissions and branch protection. The work item retains its identity even when multiple agents contribute. Factories use intake, triage, planning, building, reviewing, human handoff and completion/cancellation stages.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: epics, hierarchy, blockers, readiness, state_propagation, task_to_epic. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Epics [unknown] Not established for epics in the named first-party source pass. Product access and scenario tests were not run.
  • Hierarchy [unknown] Not established for hierarchy in the named first-party source pass. Product access and scenario tests were not run.
  • Blockers [unknown] Not established for blockers in the named first-party source pass. Product access and scenario tests were not run.
  • Readiness [unknown] Not established for readiness in the named first-party source pass. Product access and scenario tests were not run.
  • Enforcement [partial] Default spec approval is foreman instruction policy; merging is enforced by repository permissions and branch protection. Sources: warp-oz:gap07-factory-flow.
  • State propagation [unknown] Not established for state propagation in the named first-party source pass. Product access and scenario tests were not run.
  • Task to epic [unknown] Not established for task to epic in the named first-party source pass. Product access and scenario tests were not run.
  • Identity retention [supported] The work item retains its identity even when multiple agents contribute. Sources: warp-oz:gap07-factory-flow.
  • Workflow constraints [supported] Factories use intake, triage, planning, building, reviewing, human handoff and completion/cancellation stages. Sources: warp-oz:gap07-factory-flow.

Sources: warp-oz:gap07-factory-flow

Agent cross-checked partial

Cloud runs support project guidance through Rules. Reusable skills supply cloud-agent work instructions. Selecting a harness does not make all local features available in cloud; each harness keeps its own tool/context behavior.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: project_docs, memory, provenance, correction, deletion, freshness, takeover_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
10 atomic answers
  • Instructions [supported] Cloud runs support project guidance through Rules. Sources: warp-oz:gap07-cloud-rules.
  • Skills [supported] Reusable skills supply cloud-agent work instructions. Sources: warp-oz:gap07-cloud-rules.
  • Project docs [unknown] Not established for project docs in the named first-party source pass. Product access and scenario tests were not run.
  • Memory [unknown] Not established for memory in the named first-party source pass. Product access and scenario tests were not run.
  • Scope [supported] Selecting a harness does not make all local features available in cloud; each harness keeps its own tool/context behavior. Sources: warp-oz:gap07-cloud-rules.
  • Provenance [unknown] Not established for provenance in the named first-party source pass. Product access and scenario tests were not run.
  • Correction [unknown] Not established for correction in the named first-party source pass. Product access and scenario tests were not run.
  • Deletion [unknown] Not established for deletion in the named first-party source pass. Product access and scenario tests were not run.
  • Freshness [unknown] Not established for freshness in the named first-party source pass. Product access and scenario tests were not run.
  • Takeover continuity [unknown] Not established for takeover continuity in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-cloud-rules

Agent cross-checked partial

Codebase Context provides indexed repository search subject to indexing settings and harness scope.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Architecture and API awareness: first-party sources in this pass did not establish indexing, external_knowledge, multimodal_inputs, freshness, access_scope, api_retrieval, citations, conflict_detection, review_enforcement. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.
10 atomic answers
  • Indexing [unknown] Not established for indexing in the named first-party source pass. Product access and scenario tests were not run.
  • External knowledge [unknown] Not established for external knowledge in the named first-party source pass. Product access and scenario tests were not run.
  • Multimodal inputs [unknown] Not established for multimodal inputs in the named first-party source pass. Product access and scenario tests were not run.
  • Freshness [unknown] Not established for freshness in the named first-party source pass. Product access and scenario tests were not run.
  • Access scope [unknown] Not established for access scope in the named first-party source pass. Product access and scenario tests were not run.
  • Api retrieval [unknown] Not established for api retrieval in the named first-party source pass. Product access and scenario tests were not run.
  • Citations [unknown] Not established for citations in the named first-party source pass. Product access and scenario tests were not run.
  • Conflict detection [unknown] Not established for conflict detection in the named first-party source pass. Product access and scenario tests were not run.
  • Review enforcement [unknown] Not established for review enforcement in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-platform

Agent cross-checked partial

Factories accept direct requests, integration events or Factory MCP tasks. Factory MCP supports list_tasks, search_task and get_task by task URL, PR, ticket, thread or branch reference. Direct requests reach the foreman, which chooses the shortest appropriate agent-stage path. One work item can span multiple agent runs and continued/revision conversations. get_task returns status, run history and suggested isolated-worktree setup commands. Work items move through stages to Complete or Cancelled; PR handoff alone does not complete them. Direct requests and Factory MCP create work without requiring an external tracker.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: edit, discuss, prioritize, label, assign, filter, archive, reopen, project_epic_views, idea_parking. No configured product fixture was run; documentation does not establish successful hands-on behavior.
17 atomic answers
  • Create [supported] Factories accept direct requests, integration events or Factory MCP tasks. Sources: warp-oz:gap07-factory-flow.
  • Edit [unknown] Not established for edit in the named first-party source pass. Product access and scenario tests were not run.
  • Discuss [unknown] Not established for discuss in the named first-party source pass. Product access and scenario tests were not run.
  • Prioritize [unknown] Not established for prioritize in the named first-party source pass. Product access and scenario tests were not run.
  • Label [unknown] Not established for label in the named first-party source pass. Product access and scenario tests were not run.
  • Assign [unknown] Not established for assign in the named first-party source pass. Product access and scenario tests were not run.
  • Filter [unknown] Not established for filter in the named first-party source pass. Product access and scenario tests were not run.
  • Archive [unknown] Not established for archive in the named first-party source pass. Product access and scenario tests were not run.
  • Reopen [unknown] Not established for reopen in the named first-party source pass. Product access and scenario tests were not run.
  • Project epic views [unknown] Not established for project epic views in the named first-party source pass. Product access and scenario tests were not run.
  • Idea parking [unknown] Not established for idea parking in the named first-party source pass. Product access and scenario tests were not run.
  • Explicit dispatch [supported] Direct requests reach the foreman, which chooses the shortest appropriate agent-stage path. Sources: warp-oz:gap07-factory-flow.
  • Task session separation [supported] One work item can span multiple agent runs and continued/revision conversations. Sources: warp-oz:gap07-factory-flow.
  • Metadata [supported] get_task returns status, run history and suggested isolated-worktree setup commands. Sources: warp-oz:gap07-factory-mcp.
  • Durable states [supported] Work items move through stages to Complete or Cancelled; PR handoff alone does not complete them. Sources: warp-oz:gap07-factory-flow.
  • External tracker requirement [supported] Direct requests and Factory MCP create work without requiring an external tracker. Sources: warp-oz:gap07-factory-flow.

Sources: warp-oz:gap07-factory-flow, warp-oz:gap07-factory-mcp

Agent cross-checked partial

External coding agents retrieve the same task through URL, source ticket, PR or branch reference. get_task and get_conversation retrieve status, run history and foreman replies. send_task creates a factory task with title and note. External agents can hand completed pushed work back to the same factory task. MCP acts with its authenticating principal’s full permissions; no per-factory/read-only scopes exist.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: update, claim, assign, state_changes, dependencies, children, human_visibility, attribution, conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
14 atomic answers
  • Shared ids [supported] External coding agents retrieve the same task through URL, source ticket, PR or branch reference. Sources: warp-oz:gap07-factory-mcp.
  • Read [supported] get_task and get_conversation retrieve status, run history and foreman replies. Sources: warp-oz:gap07-factory-mcp.
  • Create [supported] send_task creates a factory task with title and note. Sources: warp-oz:gap07-factory-mcp.
  • Update [unknown] Not established for update in the named first-party source pass. Product access and scenario tests were not run.
  • Claim [unknown] Not established for claim in the named first-party source pass. Product access and scenario tests were not run.
  • Assign [unknown] Not established for assign in the named first-party source pass. Product access and scenario tests were not run.
  • State changes [unknown] Not established for state changes in the named first-party source pass. Product access and scenario tests were not run.
  • Dependencies [unknown] Not established for dependencies in the named first-party source pass. Product access and scenario tests were not run.
  • Children [unknown] Not established for children in the named first-party source pass. Product access and scenario tests were not run.
  • Results [supported] External agents can hand completed pushed work back to the same factory task. Sources: warp-oz:gap07-factory-mcp.
  • Human visibility [unknown] Not established for human visibility in the named first-party source pass. Product access and scenario tests were not run.
  • Attribution [unknown] Not established for attribution in the named first-party source pass. Product access and scenario tests were not run.
  • Permissions [supported] MCP acts with its authenticating principal’s full permissions; no per-factory/read-only scopes exist. Sources: warp-oz:gap07-factory-mcp.
  • Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-factory-mcp

Agent cross-checked partial

Spec agent produces behavior, technical constraints and validation criteria for a work item. Warp-managed factory definitions can be edited, validated and committed in the web app. Agents can propose a factory definition branch for review. Implementation waits for spec approval under default foreman instruction policy, which can be edited. The implement and review stages follow the work item’s specification. Inbox supports commenting on definition diffs, Request changes and Approve & merge.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: revisions, later_retrieval, drift_detection. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Persistent requirements [supported] Spec agent produces behavior, technical constraints and validation criteria for a work item. Sources: warp-oz:gap07-factory-flow.
  • Human edits [supported] Warp-managed factory definitions can be edited, validated and committed in the web app. Sources: warp-oz:gap07-dashboard.
  • Agent edits [supported] Agents can propose a factory definition branch for review. Sources: warp-oz:gap07-dashboard.
  • Revisions [unknown] Not established for revisions in the named first-party source pass. Product access and scenario tests were not run.
  • Approvals [partial] Implementation waits for spec approval under default foreman instruction policy, which can be edited. Sources: warp-oz:gap07-factory-flow.
  • Later retrieval [unknown] Not established for later retrieval in the named first-party source pass. Product access and scenario tests were not run.
  • Drift detection [unknown] Not established for drift detection in the named first-party source pass. Product access and scenario tests were not run.
  • Review integration [supported] Inbox supports commenting on definition diffs, Request changes and Approve & merge. Sources: warp-oz:gap07-dashboard.

Sources: warp-oz:gap07-factory-flow, warp-oz:gap07-dashboard

Coordination and automation

COORD-01

Parallel work

Agent cross-checked partial

Parent and child agents execute in parallel with independent conversations and run lifecycles. Fan-out/fan-in spawns multiple bounded child tasks in parallel. Orchestration is exactly one level deep; children do not spawn further children. Plan/run concurrency quotas remain unestablished. Runs show live status and nested child rows with a Sub-agents detail tab.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: observed_concurrency. No configured product fixture was run; documentation does not establish successful hands-on behavior.
5 atomic answers
  • Concurrent sessions [supported] Parent and child agents execute in parallel with independent conversations and run lifecycles. Sources: warp-oz:gap07-orchestration.
  • Concurrent tasks [supported] Fan-out/fan-in spawns multiple bounded child tasks in parallel. Sources: warp-oz:gap07-orchestration.
  • Quotas [partial] Orchestration is exactly one level deep; children do not spawn further children. Plan/run concurrency quotas remain unestablished. Sources: warp-oz:gap07-orchestration.
  • Observed concurrency [unknown] Not established for observed concurrency in the named first-party source pass. Product access and scenario tests were not run.
  • Status visibility [supported] Runs show live status and nested child rows with a Sub-agents detail tab. Sources: warp-oz:gap07-web.

Sources: warp-oz:gap07-orchestration, warp-oz:gap07-web

Agent cross-checked partial

The foreman routes work to triage, spec, implement or review agents. The foreman skips unnecessary stages and returns revisions to appropriate existing conversations.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: human_assignment, claims, queues, duplicate_prevention, ownership_enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
7 atomic answers
  • Human assignment [unknown] Not established for human assignment in the named first-party source pass. Product access and scenario tests were not run.
  • Agent assignment [supported] The foreman routes work to triage, spec, implement or review agents. Sources: warp-oz:gap07-factory-flow.
  • Claims [unknown] Not established for claims in the named first-party source pass. Product access and scenario tests were not run.
  • Queues [unknown] Not established for queues in the named first-party source pass. Product access and scenario tests were not run.
  • Routing [supported] The foreman skips unnecessary stages and returns revisions to appropriate existing conversations. Sources: warp-oz:gap07-factory-flow.
  • Duplicate prevention [unknown] Not established for duplicate prevention in the named first-party source pass. Product access and scenario tests were not run.
  • Ownership enforcement [unknown] Not established for ownership enforcement in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-factory-flow

Agent cross-checked partial

A parent spawns children for supervisor/worker, verifier, fan-out or dependency-ordered work. Ad hoc child batches select model, harness and execution settings. Parent/children exchange durable server-backed structured messages through per-agent inboxes. Children report outputs to the parent, which can combine their results. Warp Agent, Claude Code and Codex parents/children can message each other. Warp’s native parent controls child spawning and follow-up. /orchestrate or API mode:orchestrate activates the workflow. Run lifecycle events and child status update the parent and browser/app views. Parent and each child retain separate runs, transcripts, conversations and usage records. Messages can wake terminal-state children for further work. App, Oz CLI, web and API can start orchestrations.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: authentication. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Roles [supported] A parent spawns children for supervisor/worker, verifier, fan-out or dependency-ordered work. Sources: warp-oz:gap07-orchestration.
  • Model harness effort [supported] Ad hoc child batches select model, harness and execution settings. Sources: warp-oz:gap07-orchestration.
  • Messages [supported] Parent/children exchange durable server-backed structured messages through per-agent inboxes. Sources: warp-oz:gap07-orchestration.
  • Results return [supported] Children report outputs to the parent, which can combine their results. Sources: warp-oz:gap07-orchestration.
  • Cross harness [supported] Warp Agent, Claude Code and Codex parents/children can message each other. Sources: warp-oz:gap07-orchestration.
  • Orchestration owner [supported] Warp’s native parent controls child spawning and follow-up. Sources: warp-oz:gap07-orchestration.
  • Activation [supported] /orchestrate or API mode:orchestrate activates the workflow. Sources: warp-oz:gap07-orchestration.
  • Authentication [unknown] Not established for authentication in the named first-party source pass. Product access and scenario tests were not run.
  • Live progress [supported] Run lifecycle events and child status update the parent and browser/app views. Sources: warp-oz:gap07-orchestration.
  • Retained results [supported] Parent and each child retain separate runs, transcripts, conversations and usage records. Sources: warp-oz:gap07-orchestration.
  • Followup [supported] Messages can wake terminal-state children for further work. Sources: warp-oz:gap07-orchestration.
  • Invocation [supported] App, Oz CLI, web and API can start orchestrations. Sources: warp-oz:gap07-orchestration.

Sources: warp-oz:gap07-orchestration

Agent cross-checked partial

Recurring maintenance uses factory automations or standalone schedules. Factory automations and standalone integration triggers are separately configured. Cron schedules create fresh isolated runs for recurring maintenance. Each schedule runs its saved prompt or skill in a new run context; successful business outcome still depends on that prompt. Automation Platform schedules execute without a manual client trigger. After creation, runs execute automatically at the configured times.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: overlaps, retries. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Schedules [supported] Recurring maintenance uses factory automations or standalone schedules. Sources: warp-oz:nov07-platform.
  • Events [supported] Factory automations and standalone integration triggers are separately configured. Sources: warp-oz:nov07-platform.
  • Recurring tasks [supported] Cron schedules create fresh isolated runs for recurring maintenance. Sources: warp-oz:gap07-schedule-details.
  • Completion conditions [supported] Each schedule runs its saved prompt or skill in a new run context; successful business outcome still depends on that prompt. Sources: warp-oz:gap07-schedule-details.
  • Scheduler location [supported] Automation Platform schedules execute without a manual client trigger. Sources: warp-oz:gap07-schedule-details.
  • Overlaps [unknown] Not established for overlaps in the named first-party source pass. Product access and scenario tests were not run.
  • Retries [unknown] Not established for retries in the named first-party source pass. Product access and scenario tests were not run.
  • Client independence [supported] After creation, runs execute automatically at the configured times. Sources: warp-oz:gap07-schedule-details.

Sources: warp-oz:nov07-platform, warp-oz:gap07-schedule-details

Agent cross-checked partial

A run detail page has a stop action. Users can send follow-up instructions to the remote agent while its environment is active. Inbox includes asked questions and spec or PR reviews awaiting the initiating user. Run timelines and personal Inbox expose failed/blocked work. After sandbox shutdown View session opens the saved conversation transcript.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: pause, resume, notifications, escalation, chat_terminal_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
10 atomic answers
  • Pause [unknown] Not established for pause in the named first-party source pass. Product access and scenario tests were not run.
  • Stop [supported] A run detail page has a stop action. Sources: warp-oz:gap07-dashboard.
  • Resume [unknown] Not established for resume in the named first-party source pass. Product access and scenario tests were not run.
  • Steer [supported] Users can send follow-up instructions to the remote agent while its environment is active. Sources: warp-oz:nov07-sharing.
  • Notifications [unknown] Not established for notifications in the named first-party source pass. Product access and scenario tests were not run.
  • Pending decisions [supported] Inbox includes asked questions and spec or PR reviews awaiting the initiating user. Sources: warp-oz:nov07-inbox.
  • Escalation [unknown] Not established for escalation in the named first-party source pass. Product access and scenario tests were not run.
  • Visible errors [supported] Run timelines and personal Inbox expose failed/blocked work. Sources: warp-oz:gap07-dashboard.
  • Chat terminal parity [unknown] Not established for chat terminal parity in the named first-party source pass. Product access and scenario tests were not run.
  • Retained history [supported] After sandbox shutdown View session opens the saved conversation transcript. Sources: warp-oz:gap07-dashboard.

Sources: warp-oz:nov07-sharing, warp-oz:nov07-inbox, warp-oz:gap07-dashboard

Agent cross-checked partial

App status pills and browser nested rows show a parent/direct-child level. A parent can encode dependencies, wait on lifecycle events and start ready dependents. Home run views show runs you started, while Waiting on you can include PR reviews requested from you on another person’s work. Each agent retains a separate transcript and run lifecycle.

Scope
Surfaces: Warp Factories early access, Oz web app · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-21 inherited-lead additions: docs.warp.dev Platform usage, Harnesses, Factories, Factory dashboard and Factory Home pages (read 2026-11-21) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
  • Unknown after the 2026-11-21 inherited-lead recheck of first-party docs, releases and public code: fleet_fixture, navigation_errors, fixture_mode. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Fleet fixture [unknown] Not established for fleet fixture in the named first-party source pass. Product access and scenario tests were not run.
  • Parent child [supported] App status pills and browser nested rows show one parent/direct-child level. Sources: warp-oz:gap07-orchestration.
  • Dependencies [supported] A parent can encode DAG dependencies, wait on lifecycle events and start ready dependents. Sources: warp-oz:gap07-orchestration.
  • Attention [supported] Home combines personal factory run views with items directed to the current user. Waiting on you can include a PR review requested on another person’s work; run views remain limited to runs the current user started. Sources: warp-oz:ade158-home.
  • History [supported] Each agent retains a separate transcript and run lifecycle. Sources: warp-oz:gap07-orchestration.
  • Workload [supported] The factory Dashboard charts runs, opened versus merged PRs, autonomy, cycle time and cost per PR; Runs groups child runs under parents with timelines and cost; Home filters Active, Complete, Blocked and Failed. Sources: warp-oz:b07-dashboard, warp-oz:b07-home, warp-oz:b07-factories.
  • Navigation errors [unknown] Not established for navigation errors in the named first-party source pass. Product access and scenario tests were not run.
  • Fixture mode [unknown] Not established for fixture mode in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-inbox, warp-oz:gap07-orchestration, warp-oz:b07-dashboard, warp-oz:b07-home, warp-oz:b07-factories, warp-oz:ade158-home

Agent cross-checked partial

A parent can expand a task into child work and dependency-ordered execution. The parent accepts a task description that specifies child boundaries and success criteria. Batch configuration selects model, harness and execution mode.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: quick_task, presets, in_run_changes, live_roles, retained_relationships, discoverability, auth_friction. No configured product fixture was run; documentation does not establish successful hands-on behavior.
10 atomic answers
  • Quick task [unknown] Not established for quick task in the named first-party source pass. Product access and scenario tests were not run.
  • Growing epic [supported] A parent can expand a task into child work and dependency-ordered execution. Sources: warp-oz:gap07-orchestration.
  • Presets [unknown] Not established for presets in the named first-party source pass. Product access and scenario tests were not run.
  • Natural language [supported] The parent accepts a task description that specifies child boundaries and success criteria. Sources: warp-oz:gap07-orchestration.
  • Agent configuration [supported] Batch configuration selects model, harness and execution mode. Sources: warp-oz:gap07-orchestration.
  • In run changes [unknown] Not established for in run changes in the named first-party source pass. Product access and scenario tests were not run.
  • Live roles [unknown] Not established for live roles in the named first-party source pass. Product access and scenario tests were not run.
  • Retained relationships [unknown] Not established for retained relationships in the named first-party source pass. Product access and scenario tests were not run.
  • Discoverability [unknown] Not established for discoverability in the named first-party source pass. Product access and scenario tests were not run.
  • Auth friction [unknown] Not established for auth friction in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-orchestration

Execution and reliability

Sourced partial

oz agent run executes on the current dev host; unmanaged execution supports macOS, Windows and Linux. The platform routes work to configured managed workers on user infrastructure; unmanaged oz agent run is a separate mode. Enterprise managed workers run factory/standalone jobs on customer-controlled Docker, Kubernetes, Direct or external runtimes. Runs execute on configured remote hosts; the cloud agent workflow is distinct from local terminal use. Execution, inference and run-data storage are independent choices. A worker connects outbound with its worker ID and key; runs/schedules/integrations select that host. The customer provides self-hosted compute and networking. Customer workers determine available execution resources. Inactive environments shut down after an unspecified period. Remote sessions open in Warp or a browser on another device.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
  • Unknown after the targeted first-party documentation, release and repository pass: region, client_disconnect. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Local [supported] oz agent run executes on the current dev host; unmanaged execution supports macOS, Windows and Linux. Sources: warp-oz:gap07-unmanaged.
  • Byo remote [supported] The platform routes work to configured managed workers on user infrastructure; unmanaged oz agent run is a separate mode. Sources: warp-oz:nov07-platform.
  • Self hosted [supported] Enterprise managed workers run factory/standalone jobs on customer-controlled Docker, Kubernetes, Direct or external runtimes. Sources: warp-oz:gap07-workers.
  • Managed cloud [supported] Runs execute on configured remote hosts; the cloud agent workflow is distinct from local terminal use. Sources: warp-oz:nov07-platform.
  • Hybrid [supported] Execution, inference and run-data storage are independent choices. Sources: warp-oz:gap07-workers.
  • Provisioning [supported] A worker connects outbound with its worker ID and key; runs/schedules/integrations select that host. Sources: warp-oz:gap07-workers.
  • Payer [supported] The customer provides self-hosted compute and networking. Sources: warp-oz:gap07-workers.
  • Resources [supported] Customer workers determine available execution resources. Sources: warp-oz:gap07-workers.
  • Region [unknown] Not established for region in the named first-party source pass. Product access and scenario tests were not run.
  • Expiry [supported] Inactive environments shut down after an unspecified period. Sources: warp-oz:gap07-cloud-session.
  • Client disconnect [supported] Cloud handoff lets work continue without keeping the controlling laptop awake; unmanaged same-host execution is a separate mode. Sources: warp-oz:nov13-cloud-lifetime.
  • Other device continuation [supported] Remote sessions open in Warp or a browser on another device. Sources: warp-oz:gap07-cloud-session.

Sources: warp-oz:nov07-platform, warp-oz:gap07-unmanaged, warp-oz:gap07-workers, warp-oz:gap07-cloud-session, warp-oz:nov13-cloud-lifetime

Sourced partial

Configured environments clone the authorized repositories. Task-specific branches derive from OZ_RUN_ID. A documented Direct-worker pattern creates one Git worktree and branch per task through setup hooks. Docker runs each task in a container; Kubernetes uses one Job per task. Containers prefer an image non-root user or dedicated agent with passwordless sudo; setup failure can continue as root. Cloud-local children share the parent environment/filesystem; separate-cloud children get separate environments. Direct tasks share the worker host’s processes and network; worktrees do not create an OS security boundary. Workers connect outbound to Warp; task assignment requires no inbound port. Worker keys authenticate the execution host; customer controls runtime secrets. Shared-host agents require distinct worktrees/branches; different prompts alone do not isolate files. Customer compute does not eliminate Warp control-plane or prompt/transcript data flows.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
  • Unknown after the targeted first-party documentation, release and repository pass: vm. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Checkout [supported] Configured environments clone the authorized repositories. Sources: warp-oz:gap07-environment.
  • Branch [supported] Task-specific branches derive from OZ_RUN_ID. Sources: warp-oz:gap07-worktrees.
  • Worktree [supported] A documented Direct-worker pattern creates one Git worktree and branch per task through setup hooks. Sources: warp-oz:gap07-worktrees.
  • Container [supported] Docker runs each task in a container; Kubernetes uses one Job per task. Sources: warp-oz:gap07-workers.
  • Vm [supported] The vendor cloud session viewer explicitly describes tasks running on remote virtual machines. Customer-managed Direct and container workers remain separate modes. Sources: warp-oz:nov13-cloud-vm.
  • Os sandbox [partial] Containers prefer an image non-root user or dedicated agent with passwordless sudo; setup failure can continue as root. Sources: warp-oz:gap07-environment.
  • Filesystem [partial] Cloud-local children share the parent environment/filesystem; separate-cloud children get separate environments. Sources: warp-oz:gap07-orchestration.
  • Process [partial] Direct tasks share the worker host’s processes and network; worktrees do not create an OS security boundary. Sources: warp-oz:gap07-worktrees.
  • Network [supported] Workers connect outbound to Warp; task assignment requires no inbound port. Sources: warp-oz:gap07-workers.
  • Secrets [supported] Worker keys authenticate the execution host; customer controls runtime secrets. Sources: warp-oz:gap07-workers.
  • Code separation [partial] Shared-host agents require distinct worktrees/branches; different prompts alone do not isolate files. Sources: warp-oz:gap07-orchestration.
  • Security boundary [partial] Customer compute does not eliminate Warp control-plane or prompt/transcript data flows. Sources: warp-oz:gap07-workers.

Sources: warp-oz:gap07-environment, warp-oz:gap07-worktrees, warp-oz:gap07-workers, warp-oz:gap07-orchestration, warp-oz:nov13-cloud-vm

Agent cross-checked partial

Inactive cloud environments shut down; continuation then uses Fork to local rather than reconnecting to a stopped VM. Cloud conversation history remains inspectable through the session link. Followups reuse an active remote environment; after shutdown Fork to local continues the conversation. Conversation transfer does not automatically transfer every remote branch or live process. Forked code work can require manually cloning the remotely-created branch.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: client_disconnect, worker_crash, service_restart, process_reconnect, state_reconstruction, duplicate_actions, multi_day_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Client disconnect [unknown] Not established for client disconnect in the named first-party source pass. Product access and scenario tests were not run.
  • Worker crash [unknown] Not established for worker crash in the named first-party source pass. Product access and scenario tests were not run.
  • Service restart [unknown] Not established for service restart in the named first-party source pass. Product access and scenario tests were not run.
  • Expiry [supported] Inactive cloud environments shut down; continuation then uses Fork to local rather than reconnecting to a stopped VM. Sources: warp-oz:nov07-sharing.
  • Transcript reload [supported] Cloud conversation history remains inspectable through the session link. Sources: warp-oz:gap07-cloud-session.
  • Process reconnect [unknown] Not established for process reconnect in the named first-party source pass. Product access and scenario tests were not run.
  • Task resume [partial] Followups reuse an active remote environment; after shutdown Fork to local continues the conversation. Sources: warp-oz:gap07-cloud-session.
  • State reconstruction [unknown] Not established for state reconstruction in the named first-party source pass. Product access and scenario tests were not run.
  • Context loss [partial] Conversation transfer does not automatically transfer every remote branch or live process. Sources: warp-oz:gap07-cloud-session.
  • Duplicate actions [unknown] Not established for duplicate actions in the named first-party source pass. Product access and scenario tests were not run.
  • Manual repair [supported] Forked code work can require manually cloning the remotely-created branch. Sources: warp-oz:gap07-cloud-session.
  • Multi day continuity [unknown] Not established for multi day continuity in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-sharing, warp-oz:gap07-cloud-session

Agent cross-checked partial

Environment images and setup commands define the toolchain and install steps. Each scheduled run begins in a clean isolated environment rather than reusing the previous run’s context. Factory secrets or standalone Agent Secrets supply setup credentials. Docs recommend repeatable setup and pinned toolchains; automatic setup deduplication is not established. /create-environment inspects repo languages and proposes image/setup configuration.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: caches, services, ports, collisions, automatic_repair. No configured product fixture was run; documentation does not establish successful hands-on behavior.
10 atomic answers
  • Dependencies [supported] Environment images and setup commands define the toolchain and install steps. Sources: warp-oz:gap07-environment.
  • Caches [unknown] Not established for caches in the named first-party source pass. Product access and scenario tests were not run.
  • Snapshots [partial] Each scheduled run begins in a clean isolated environment rather than reusing the previous run’s context. Sources: warp-oz:gap07-schedule-details.
  • Services [unknown] Not established for services in the named first-party source pass. Product access and scenario tests were not run.
  • Ports [unknown] Not established for ports in the named first-party source pass. Product access and scenario tests were not run.
  • Secrets [supported] Factory secrets or standalone Agent Secrets supply setup credentials. Sources: warp-oz:gap07-environment.
  • Duplicate installs [partial] Docs recommend repeatable setup and pinned toolchains; automatic setup deduplication is not established. Sources: warp-oz:gap07-environment.
  • Collisions [unknown] Not established for collisions in the named first-party source pass. Product access and scenario tests were not run.
  • Remote setup [supported] /create-environment inspects repo languages and proposes image/setup configuration. Sources: warp-oz:gap07-environment.
  • Automatic repair [unknown] Not established for automatic repair in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-environment, warp-oz:gap07-schedule-details

Agent cross-checked partial

Worker idle-on-complete defaults forty-five minutes unless overridden; direct Agent API runs default ten minutes. One-shot Direct workers force maximum concurrency one and exit after the accepted task terminates.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: time_limits, turn_limits, token_limits, spend_limits, retries, provider_failures. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Time limits [unknown] Not established for time limits in the named first-party source pass. Product access and scenario tests were not run.
  • Turn limits [unknown] Not established for turn limits in the named first-party source pass. Product access and scenario tests were not run.
  • Token limits [unknown] Not established for token limits in the named first-party source pass. Product access and scenario tests were not run.
  • Spend limits [unknown] Not established for spend limits in the named first-party source pass. Product access and scenario tests were not run.
  • Timeouts [supported] Worker idle-on-complete defaults forty-five minutes unless overridden; direct Agent API runs default ten minutes. Sources: warp-oz:gap07-worker-controls.
  • Retries [unknown] Not established for retries in the named first-party source pass. Product access and scenario tests were not run.
  • Provider failures [unknown] Not established for provider failures in the named first-party source pass. Product access and scenario tests were not run.
  • Enforcement [supported] One-shot Direct workers force maximum concurrency one and exit after the accepted task terminates. Sources: warp-oz:gap07-worker-controls.

Sources: warp-oz:gap07-worker-controls

Agent cross-checked partial

Run detail panes expose transcripts and outputs. Failure states and transcripts are inspectable; a standardized root-cause diagnosis is not established. Runs list environment, creator, source, artifacts and cost/credits. Runs can expose subagents and their independent details. Dashboard includes factory autonomy, PR cycle time, opened/merged PRs and cost-per-PR metrics. Runs can be filtered by date range. Run states include working, succeeded, failed, canceled, errored and blocked. Inbox links questions/spec approvals/PR reviews awaiting human attention.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: traces, usage_export, reconnect_consistency, performance_method, responsiveness. No configured product fixture was run; documentation does not establish successful hands-on behavior.
13 atomic answers
  • Logs [supported] Run detail panes expose transcripts and outputs. Sources: warp-oz:gap07-web.
  • Traces [unknown] Not established for traces in the named first-party source pass. Product access and scenario tests were not run.
  • Failure reasons [partial] Failure states and transcripts are inspectable; a standardized root-cause diagnosis is not established. Sources: warp-oz:gap07-web.
  • Usage export [unknown] Not established for usage export in the named first-party source pass. Product access and scenario tests were not run.
  • Task stats [supported] Runs list environment, creator, source, artifacts and cost/credits. Sources: warp-oz:gap07-web.
  • Agent stats [supported] Runs can expose subagents and their independent details. Sources: warp-oz:gap07-dashboard.
  • Project stats [supported] Dashboard includes factory autonomy, PR cycle time, opened/merged PRs and cost-per-PR metrics. Sources: warp-oz:gap07-dashboard.
  • Time stats [supported] Runs can be filtered by date range. Sources: warp-oz:gap07-web.
  • Failure status [supported] Run states include working, succeeded, failed, canceled, errored and blocked. Sources: warp-oz:gap07-web.
  • Approval status [supported] Inbox links questions/spec approvals/PR reviews awaiting human attention. Sources: warp-oz:gap07-dashboard.
  • Reconnect consistency [unknown] Not established for reconnect consistency in the named first-party source pass. Product access and scenario tests were not run.
  • Performance method [unknown] Not established for performance method in the named first-party source pass. Product access and scenario tests were not run.
  • Responsiveness [unknown] Not established for responsiveness in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-web, warp-oz:gap07-dashboard

Agent cross-checked partial

Run pages expose a timeline and cost. Factory cost-per-PR includes a run’s children and apportions cost across generated PRs. Dashboard cost-per-PR is an estimate, not an invoice total. Warp explicitly says external inference bills are not fully represented in its summaries. Cost-per-PR expands to show the most expensive PRs over the selected date range.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: task_cost, epic_cost, harness_aggregation, tokens, subscription_allowance, compute_cost, refresh_delay, alerts, export. No configured product fixture was run; documentation does not establish successful hands-on behavior.
14 atomic answers
  • Task cost [unknown] Not established for task cost in the named first-party source pass. Product access and scenario tests were not run.
  • Session cost [supported] Run pages expose a timeline and cost. Sources: warp-oz:gap07-dashboard.
  • Child cost [supported] Factory cost-per-PR includes a run’s children and apportions cost across generated PRs. Sources: warp-oz:gap07-dashboard.
  • Epic cost [unknown] Not established for epic cost in the named first-party source pass. Product access and scenario tests were not run.
  • Harness aggregation [unknown] Not established for harness aggregation in the named first-party source pass. Product access and scenario tests were not run.
  • Billed vs estimated [supported] Dashboard cost-per-PR is an estimate, not an invoice total. Sources: warp-oz:gap07-dashboard.
  • Tokens [unknown] Not established for tokens in the named first-party source pass. Product access and scenario tests were not run.
  • Subscription allowance [unknown] Not established for subscription allowance in the named first-party source pass. Product access and scenario tests were not run.
  • Provider reconciliation [supported] Warp explicitly says external inference bills are not fully represented in its summaries. Sources: warp-oz:nov07-harnesses.
  • Compute cost [unknown] Not established for compute cost in the named first-party source pass. Product access and scenario tests were not run.
  • Refresh delay [unknown] Not established for refresh delay in the named first-party source pass. Product access and scenario tests were not run.
  • Alerts [unknown] Not established for alerts in the named first-party source pass. Product access and scenario tests were not run.
  • Export [unknown] Not established for export in the named first-party source pass. Product access and scenario tests were not run.
  • Drilldown [supported] Cost-per-PR expands to show the most expensive PRs over the selected date range. Sources: warp-oz:gap07-dashboard.

Sources: warp-oz:nov07-harnesses, warp-oz:gap07-dashboard

Agent cross-checked partial

Managed workers support --max-concurrent-tasks; zero defaults to unlimited. Tasks above the configured worker concurrency wait for a free slot. Kubernetes preflight/resources and task-container limits are configurable. Worker concurrency caps delay admission instead of starting all tasks immediately.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: host_awareness, check_reuse, check_deduplication, bounded_tests, cancellation, fairness, recovery, shared_limits. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Concurrency [supported] Managed workers support --max-concurrent-tasks; zero defaults to unlimited. Sources: warp-oz:gap07-worker-controls.
  • Queues [supported] Tasks above the configured worker concurrency wait for a free slot. Sources: warp-oz:gap07-worker-controls.
  • Cpu ram [supported] Kubernetes preflight/resources and task-container limits are configurable. Sources: warp-oz:gap07-worker-controls.
  • Backpressure [supported] Worker concurrency caps delay admission instead of starting all tasks immediately. Sources: warp-oz:gap07-worker-controls.
  • Host awareness [unknown] Not established for host awareness in the named first-party source pass. Product access and scenario tests were not run.
  • Check reuse [unknown] Not established for check reuse in the named first-party source pass. Product access and scenario tests were not run.
  • Check deduplication [unknown] Not established for check deduplication in the named first-party source pass. Product access and scenario tests were not run.
  • Bounded tests [unknown] Not established for bounded tests in the named first-party source pass. Product access and scenario tests were not run.
  • Cancellation [unknown] Not established for cancellation in the named first-party source pass. Product access and scenario tests were not run.
  • Fairness [unknown] Not established for fairness in the named first-party source pass. Product access and scenario tests were not run.
  • Recovery [unknown] Not established for recovery in the named first-party source pass. Product access and scenario tests were not run.
  • Shared limits [unknown] Not established for shared limits in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-worker-controls

Human collaboration and control

Agent cross-checked partial

Shared links expose the remote conversation, commands, logs and outputs to authorized teammates. --share team:edit or user:edit grants collaborators read/write access to steer the same running session. --share targets individual users or the team with explicit view/edit access. Agent-key runs automatically have team scope; sharing still follows account authorization.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: discussion, comments, presence, ordering, conflicts, attribution, owner_online. No configured product fixture was run; documentation does not establish successful hands-on behavior.
11 atomic answers
  • Visibility [supported] Shared links expose the remote conversation, commands, logs and outputs to authorized teammates. Sources: warp-oz:nov07-sharing, warp-oz:nov07-platform.
  • Discussion [unknown] Not established for discussion in the named first-party source pass. Product access and scenario tests were not run.
  • Comments [unknown] Not established for comments in the named first-party source pass. Product access and scenario tests were not run.
  • Presence [unknown] Not established for presence in the named first-party source pass. Product access and scenario tests were not run.
  • Coprompting [supported] --share team:edit or user:edit grants collaborators read/write access to steer the same running session. Sources: warp-oz:gap07-unmanaged.
  • Ordering [unknown] Not established for ordering in the named first-party source pass. Product access and scenario tests were not run.
  • Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.
  • Attribution [unknown] Not established for attribution in the named first-party source pass. Product access and scenario tests were not run.
  • Permissions [supported] --share targets individual users or the team with explicit view/edit access. Sources: warp-oz:gap07-unmanaged.
  • Plan restrictions [supported] Agent-key runs automatically have team scope; sharing still follows account authorization. Sources: warp-oz:gap07-unmanaged.
  • Owner online [unknown] Not established for owner online in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-sharing, warp-oz:nov07-platform, warp-oz:gap07-unmanaged

Agent cross-checked partial

Inherited Owner/Admin permissions govern administration; factory roles include Factory user and Editor. Enterprise can assign a factory-specific user/Editor role overriding team defaults. Admins assign team-wide and per-factory roles. Business lists SAML SSO; Enterprise adds further administration controls. Factory users can run/view but cannot edit definitions, agents or automations. Granular factory role assignment requires Enterprise; other plans give members Editor access.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: task_roles, provisioning, revocation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Organization roles [supported] Inherited Owner/Admin permissions govern administration; factory roles include Factory user and Editor. Sources: warp-oz:gap07-roles.
  • Project roles [supported] Enterprise can assign a factory-specific user/Editor role overriding team defaults. Sources: warp-oz:gap07-roles.
  • Task roles [unknown] Not established for task roles in the named first-party source pass. Product access and scenario tests were not run.
  • Membership [supported] Admins assign team-wide and per-factory roles. Sources: warp-oz:gap07-roles.
  • Sso [supported] Business lists SAML SSO; Enterprise adds further administration controls. Sources: warp-oz:nov07-pricing.
  • Provisioning [unknown] Not established for provisioning in the named first-party source pass. Product access and scenario tests were not run.
  • Unauthorized access [supported] Factory users can run/view but cannot edit definitions, agents or automations. Sources: warp-oz:gap07-roles.
  • Revocation [unknown] Not established for revocation in the named first-party source pass. Product access and scenario tests were not run.
  • Plan scope [supported] Granular factory role assignment requires Enterprise; other plans give members Editor access. Sources: warp-oz:gap07-roles.

Sources: warp-oz:nov07-pricing, warp-oz:gap07-roles

Agent cross-checked partial

Factory role does not confer repository merge rights. Repository permissions and branch protection govern PR approval and merging; foreman instructions govern specification approval.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: command, tool, network, secret, approver_identity, lifetime, allow, deny, revoke, tunnels, defaults, safer_modes. No configured product fixture was run; documentation does not establish successful hands-on behavior.
14 atomic answers
  • Command [unknown] Not established for command in the named first-party source pass. Product access and scenario tests were not run.
  • Tool [unknown] Not established for tool in the named first-party source pass. Product access and scenario tests were not run.
  • Network [unknown] Not established for network in the named first-party source pass. Product access and scenario tests were not run.
  • Secret [unknown] Not established for secret in the named first-party source pass. Product access and scenario tests were not run.
  • Delivery [supported] Factory role does not confer repository merge rights. Sources: warp-oz:gap07-roles.
  • Approver identity [unknown] Not established for approver identity in the named first-party source pass. Product access and scenario tests were not run.
  • Lifetime [unknown] Not established for lifetime in the named first-party source pass. Product access and scenario tests were not run.
  • Allow [unknown] Not established for allow in the named first-party source pass. Product access and scenario tests were not run.
  • Deny [unknown] Not established for deny in the named first-party source pass. Product access and scenario tests were not run.
  • Revoke [unknown] Not established for revoke in the named first-party source pass. Product access and scenario tests were not run.
  • Tunnels [unknown] Not established for tunnels in the named first-party source pass. Product access and scenario tests were not run.
  • Defaults [unknown] Not established for defaults in the named first-party source pass. Product access and scenario tests were not run.
  • Safer modes [unknown] Not established for safer modes in the named first-party source pass. Product access and scenario tests were not run.
  • Enforcement [supported] Repository permissions and branch protection govern PR approval and merging; foreman instructions govern specification approval. Sources: warp-oz:gap07-roles.

Sources: warp-oz:gap07-roles

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Agent cross-checked partial

Home shows questions, specs and PR reviews awaiting the current user. Rows open detail panes and linked runs, PRs, specs or originating tickets.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-21 inherited-lead additions: docs.warp.dev Platform usage, Harnesses, Factories, Factory dashboard and Factory Home pages (read 2026-11-21) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
  • Unknown after the 2026-11-21 inherited-lead recheck of first-party docs, releases and public code: change_understanding, comments, request_changes, shipping_guidance, effort, missed_evidence, keyboard, narrow_screen, context_switching, retained_context. No configured product fixture was run; documentation does not establish successful hands-on behavior.
  • Human visibility of Home and Runs does not establish clarity of agent roles during review.
13 atomic answers
  • Pending reviews [supported] Inbox shows questions, specs and PR reviews awaiting the current user. Sources: warp-oz:gap07-inbox.
  • Change understanding [unknown] Not established for change understanding in the named first-party source pass. Product access and scenario tests were not run.
  • Evidence navigation [supported] Rows open detail panes and linked runs, PRs, specs or originating tickets. Sources: warp-oz:gap07-inbox.
  • Comments [unknown] Not established for comments in the named first-party source pass. Product access and scenario tests were not run.
  • Request changes [unknown] Not established for request changes in the named first-party source pass. Product access and scenario tests were not run.
  • Shipping guidance [unknown] Not established for shipping guidance in the named first-party source pass. Product access and scenario tests were not run.
  • Effort [unknown] Not established for effort in the named first-party source pass. Product access and scenario tests were not run.
  • Missed evidence [unknown] Not established for missed evidence in the named first-party source pass. Product access and scenario tests were not run.
  • Keyboard [unknown] Not established for keyboard in the named first-party source pass. Product access and scenario tests were not run.
  • Narrow screen [unknown] Not established for narrow screen in the named first-party source pass. Product access and scenario tests were not run.
  • Context switching [unknown] Not established for context switching in the named first-party source pass. Product access and scenario tests were not run.
  • Roles [unknown] Agent-role clarity is not established by the cited Home and dashboard pages. They describe human visibility and run access, which do not answer how agent roles are distinguished during review.
  • Retained context [unknown] Not established for retained context in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-sharing, warp-oz:nov07-inbox, warp-oz:gap07-inbox, warp-oz:b07-home, warp-oz:b07-dashboard

Agent cross-checked partial

Authorized users send follow-up instructions through a shared active cloud session. Follow-up chat continues the remote agent conversation. Review includes prompt, plan, decisions, commands and logs. The remote environment remains usable only while active; after shutdown the workflow forks locally. Fork to local transfers the conversation; a remote-created branch may need to be cloned manually. This is not tested same-runtime human takeover.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: decisions, artifacts, permissions, owner_disconnect, ownership, attribution, context_loss. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Ongoing takeover [supported] Authorized users send follow-up instructions through a shared active cloud session. Sources: warp-oz:gap07-cloud-session.
  • Same task [supported] Follow-up chat continues the remote agent conversation. Sources: warp-oz:gap07-cloud-session.
  • Session history [supported] Review includes prompt, plan, decisions, commands and logs. Sources: warp-oz:gap07-cloud-session.
  • Decisions [unknown] Not established for decisions in the named first-party source pass. Product access and scenario tests were not run.
  • Artifacts [unknown] Not established for artifacts in the named first-party source pass. Product access and scenario tests were not run.
  • Permissions [unknown] Not established for permissions in the named first-party source pass. Product access and scenario tests were not run.
  • Runtime context [partial] The remote environment remains usable only while active; after shutdown the workflow forks locally. Sources: warp-oz:gap07-cloud-session.
  • Owner disconnect [unknown] Not established for owner disconnect in the named first-party source pass. Product access and scenario tests were not run.
  • Ownership [unknown] Not established for ownership in the named first-party source pass. Product access and scenario tests were not run.
  • Attribution [unknown] Not established for attribution in the named first-party source pass. Product access and scenario tests were not run.
  • Context loss [unknown] Not established for context loss in the named first-party source pass. Product access and scenario tests were not run.
  • Harness transfer [supported] Fork to local transfers the conversation; a remote-created branch may need to be cloned manually. This is not tested same-runtime human takeover. Sources: warp-oz:nov07-sharing.

Sources: warp-oz:nov07-sharing, warp-oz:gap07-cloud-session

Verification and delivery

Sourced partial

Shared runs expose Computer Use artifacts when produced. The shared session may include Computer Use artifacts; no cross-task gallery or retention test was run. Remote context and generated output can be inspected through the session viewer. Runs carry shareable session links. Parent/child conversations can be inspected separately from their run views.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
  • Unknown after the targeted first-party documentation, release and repository pass: diffs, documents, test_outputs, reviewer_outputs, gallery, revision_links, persistence, prompt_leakage. No configured product fixture was run; documentation does not establish successful hands-on behavior.
13 atomic answers
  • Diffs [partial] The shared session lets users review the code/config changes produced by the cloud agent; no full cross-task diff workflow is established. Sources: warp-oz:nov13-cloud-vm.
  • Documents [unknown] Not established for documents in the named first-party source pass. Product access and scenario tests were not run.
  • Screenshots [supported] Shared runs expose Computer Use artifacts when produced. Sources: warp-oz:gap07-cloud-session.
  • Recordings [supported] The shared session may include Computer Use artifacts; no cross-task gallery or retention test was run. Sources: warp-oz:nov07-sharing.
  • Previews [supported] Remote context and generated output can be inspected through the session viewer. Sources: warp-oz:gap07-cloud-session.
  • Test outputs [unknown] Not established for test outputs in the named first-party source pass. Product access and scenario tests were not run.
  • Reviewer outputs [unknown] Not established for reviewer outputs in the named first-party source pass. Product access and scenario tests were not run.
  • Persistence [unknown] Not established for persistence in the named first-party source pass. Product access and scenario tests were not run.
  • Child findings [supported] Parent/child conversations can be inspected separately from their run views. Sources: warp-oz:gap07-cloud-session.
  • Prompt leakage [unknown] Not established for prompt leakage in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-sharing, warp-oz:gap07-cloud-session, warp-oz:nov13-cloud-vm

Agent cross-checked partial

A separate review agent checks requirements, tests and security expectations. Review compares changes with requirements and validation criteria. Agent review verdicts are advisory; spec/question pauses are configurable instruction policy. Repository controls must enforce human-only merging.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: tests, lint, types, ci, required_checks, failure_blocking, requirement_conflicts, configured_policy. No configured product fixture was run; documentation does not establish successful hands-on behavior.
11 atomic answers
  • Tests [unknown] Not established for tests in the named first-party source pass. Product access and scenario tests were not run.
  • Lint [unknown] Not established for lint in the named first-party source pass. Product access and scenario tests were not run.
  • Types [unknown] Not established for types in the named first-party source pass. Product access and scenario tests were not run.
  • Ci [unknown] Not established for ci in the named first-party source pass. Product access and scenario tests were not run.
  • Independent review [supported] A separate review agent checks requirements, tests and security expectations. Sources: warp-oz:gap07-factory-flow.
  • Spec checks [supported] Review compares changes with requirements and validation criteria. Sources: warp-oz:gap07-factory-flow.
  • Required checks [unknown] Not established for required checks in the named first-party source pass. Product access and scenario tests were not run.
  • Failure blocking [unknown] Not established for failure blocking in the named first-party source pass. Product access and scenario tests were not run.
  • Requirement conflicts [unknown] Not established for requirement conflicts in the named first-party source pass. Product access and scenario tests were not run.
  • Configured policy [unknown] Not established for configured policy in the named first-party source pass. Product access and scenario tests were not run.
  • Enforced policy [partial] Agent review verdicts are advisory; spec/question pauses are configurable instruction policy. Repository controls must enforce human-only merging. Sources: warp-oz:gap07-factory-flow.

Sources: warp-oz:gap07-factory-flow

Agent cross-checked partial

The implement agent works on a branch. The implement agent opens a pull request with test and visual evidence. The work item completes after a merge notification or human confirmation that the PR landed.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: worktrees, commits, comments, ci_response, rebase, conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Branches [supported] The implement agent works on a branch. Sources: warp-oz:gap07-factory-flow.
  • Worktrees [unknown] Not established for worktrees in the named first-party source pass. Product access and scenario tests were not run.
  • Commits [unknown] Not established for commits in the named first-party source pass. Product access and scenario tests were not run.
  • Pull requests [supported] The implement agent opens a pull request with test and visual evidence. Sources: warp-oz:gap07-factory-flow.
  • Comments [unknown] Not established for comments in the named first-party source pass. Product access and scenario tests were not run.
  • Ci response [unknown] Not established for ci response in the named first-party source pass. Product access and scenario tests were not run.
  • Rebase [unknown] Not established for rebase in the named first-party source pass. Product access and scenario tests were not run.
  • Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.
  • Product state [supported] The work item completes after a merge notification or human confirmation that the PR landed. Sources: warp-oz:gap07-factory-flow.

Sources: warp-oz:gap07-factory-flow

Agent cross-checked partial

A person decides when/whether to merge; branch protection and repository permissions enforce that boundary. Factory instructions alone do not enforce human-only merge; repository access controls are required.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: approve, release, deploy, exact_revision. No configured product fixture was run; documentation does not establish successful hands-on behavior.
6 atomic answers
  • Approve [unknown] Not established for approve in the named first-party source pass. Product access and scenario tests were not run.
  • Merge [partial] A person decides when/whether to merge; branch protection and repository permissions enforce that boundary. Sources: warp-oz:gap07-factory-flow.
  • Release [unknown] Not established for release in the named first-party source pass. Product access and scenario tests were not run.
  • Deploy [unknown] Not established for deploy in the named first-party source pass. Product access and scenario tests were not run.
  • Exact revision [unknown] Not established for exact revision in the named first-party source pass. Product access and scenario tests were not run.
  • Authority enforcement [partial] Factory instructions alone do not enforce human-only merge; repository access controls are required. Sources: warp-oz:gap07-factory-flow.

Sources: warp-oz:gap07-factory-flow

Agent cross-checked partial

Factory handoff presents pull requests and evidence linked to the originating work item. The default foreman waits for a merge notification or confirmation before marking Complete. Work-item source context persists through stages and the human handoff.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: commit_links, build_links, deployment_links, rollback, revert, stale_approval_invalidation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Delivery status [supported] The default foreman waits for a merge notification or confirmation before marking Complete. Sources: warp-oz:gap07-factory-flow.
  • Retained evidence [supported] Work-item source context persists through stages and the human handoff. Sources: warp-oz:gap07-factory-flow.
  • Rollback [unknown] Not established for rollback in the named first-party source pass. Product access and scenario tests were not run.
  • Revert [unknown] Not established for revert in the named first-party source pass. Product access and scenario tests were not run.
  • Stale approval invalidation [unknown] Not established for stale approval invalidation in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-factory-flow

Agent cross-checked partial

Factory Inbox collects the current user’s question, spec-review and PR-review items. Inbox filters by factory, kind and read state and searches title/descriptions. This is a personal attention queue for self-started tasks, not a team-wide dependency queue. Rows link the run, PR, spec or source ticket; items can be marked resolved with Undo.

Scope
Surfaces: Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: summaries, risk_size_filters, findings, artifacts, request_changes, exact_revision_approval, stale_approval_invalidation, check_deduplication. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Review queue [supported] Factory Inbox collects the current user’s question, spec-review and PR-review items. Sources: warp-oz:gap07-inbox.
  • Summaries [unknown] Not established for summaries in the named first-party source pass. Product access and scenario tests were not run.
  • Grouping [supported] Inbox filters by factory, kind and read state and searches title/descriptions. Sources: warp-oz:gap07-inbox.
  • Risk size filters [unknown] Not established for risk size filters in the named first-party source pass. Product access and scenario tests were not run.
  • Findings [unknown] Not established for findings in the named first-party source pass. Product access and scenario tests were not run.
  • Artifacts [unknown] Not established for artifacts in the named first-party source pass. Product access and scenario tests were not run.
  • Request changes [unknown] Not established for request changes in the named first-party source pass. Product access and scenario tests were not run.
  • Exact revision approval [unknown] Not established for exact revision approval in the named first-party source pass. Product access and scenario tests were not run.
  • Dependency queues [partial] This is a personal attention queue for self-started tasks, not a team-wide dependency queue. Sources: warp-oz:gap07-inbox.
  • Next actions [supported] Rows link the run, PR, spec or source ticket; items can be marked resolved with Undo. Sources: warp-oz:gap07-inbox.
  • Stale approval invalidation [unknown] Not established for stale approval invalidation in the named first-party source pass. Product access and scenario tests were not run.
  • Check deduplication [unknown] Not established for check deduplication in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-inbox, warp-oz:gap07-inbox

Ownership, privacy and economics

Agent cross-checked partial

Hosted Warp services use the vendor’s product/services license agreement with limited access and copying/redistribution restrictions. Third-party dependencies or client licenses do not replace the hosted service agreement.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: client_license, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
6 atomic answers
  • Client license [unknown] Not established for client license in the named first-party source pass. Product access and scenario tests were not run.
  • Server license [supported] Hosted Warp services use the vendor’s product/services license agreement with limited access and copying/redistribution restrictions. Sources: warp-oz:gap07-license.
  • Hosted extensions [supported] Third-party dependencies or client licenses do not replace the hosted service agreement. Sources: warp-oz:gap07-license.
  • Source visibility [unknown] Not established for source visibility in the named first-party source pass. Product access and scenario tests were not run.
  • Source revision [unknown] Not established for source revision in the named first-party source pass. Product access and scenario tests were not run.
  • Hosted parity [unknown] Not established for hosted parity in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-license

Agent cross-checked partial

Customer-hosted workers execute jobs, but Warp hosts routing, tracking and control-plane metadata; the complete core platform is not self-hosted. Warp control plane remains required even with customer execution and separate transcript storage.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: export, import, formats, cancellation, account_independence, history_portability. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Self hosting [partial] Customer-hosted workers execute jobs, but Warp hosts routing, tracking and control-plane metadata; the complete core platform is not self-hosted. Sources: warp-oz:gap07-workers.
  • Vendor dependencies [supported] Warp control plane remains required even with customer execution and separate transcript storage. Sources: warp-oz:gap07-workers.
  • Export [unknown] Not established for export in the named first-party source pass. Product access and scenario tests were not run.
  • Import [unknown] Not established for import in the named first-party source pass. Product access and scenario tests were not run.
  • Formats [unknown] Not established for formats in the named first-party source pass. Product access and scenario tests were not run.
  • Cancellation [unknown] Not established for cancellation in the named first-party source pass. Product access and scenario tests were not run.
  • Account independence [unknown] Not established for account independence in the named first-party source pass. Product access and scenario tests were not run.
  • History portability [unknown] Not established for history portability in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:gap07-workers

Agent cross-checked partial

Warp retains control-plane operational logs, configuration, run metadata and billing records. Transcripts, artifacts and prompt attachments use Warp-managed storage unless configured to a customer bucket. Warp Agent inference routes through Warp; Claude Code/Codex call providers directly from the execution environment.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: code_data, prompts, credentials, retention, deletion, training, residency, subprocessors, telemetry_disclosure, telemetry_defaults, telemetry_controls, consent_prompt. No configured product fixture was run; documentation does not establish successful hands-on behavior.
15 atomic answers
  • Code data [unknown] Not established for code data in the named first-party source pass. Product access and scenario tests were not run.
  • Prompts [unknown] Not established for prompts in the named first-party source pass. Product access and scenario tests were not run.
  • Credentials [unknown] Not established for credentials in the named first-party source pass. Product access and scenario tests were not run.
  • Logs [supported] Warp retains control-plane operational logs, configuration, run metadata and billing records. Sources: warp-oz:gap07-workers.
  • Artifacts [supported] Transcripts, artifacts and prompt attachments use Warp-managed storage unless configured to a customer bucket. Sources: warp-oz:gap07-workers.
  • Retention [unknown] Not established for retention in the named first-party source pass. Product access and scenario tests were not run.
  • Deletion [unknown] Not established for deletion in the named first-party source pass. Product access and scenario tests were not run.
  • Training [unknown] Not established for training in the named first-party source pass. Product access and scenario tests were not run.
  • Residency [unknown] Not established for residency in the named first-party source pass. Product access and scenario tests were not run.
  • Subprocessors [unknown] Not established for subprocessors in the named first-party source pass. Product access and scenario tests were not run.
  • Telemetry disclosure [unknown] Not established for telemetry disclosure in the named first-party source pass. Product access and scenario tests were not run.
  • Telemetry defaults [unknown] Not established for telemetry defaults in the named first-party source pass. Product access and scenario tests were not run.
  • Telemetry controls [unknown] Not established for telemetry controls in the named first-party source pass. Product access and scenario tests were not run.
  • Provider separation [supported] Warp Agent inference routes through Warp; Claude Code/Codex call providers directly from the execution environment. Sources: warp-oz:gap07-workers.

Sources: warp-oz:gap07-workers

Agent cross-checked partial

Build is $20/month monthly or $18/month annually. Max is $200 monthly or $180/month annually. Business is $50/user/month monthly or $45 annually, checked 7 November 2026. Build includes $20 agent usage monthly; Max includes $200; Business includes $20 per seat. Compute and platform charges require separate checks. Further scoped facts are recorded in the atomic answers.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app · Version: Earlier findings: Public sources checked 2026-11-07; no installed release tested; 2026-11-21 inherited-lead additions: docs.warp.dev Platform usage, Harnesses, Factories, Factory dashboard and Factory Home pages (read 2026-11-21) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Price and included usage: first-party sources in this pass did not establish currency, seats, seat_minimum, workspace_fees, credits, trial, overages, taxes. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
  • Warp Factories has a separate price table: pay as you go, Build, Business and Enterprise, with no Max plan or annual price shown, and factory usage billed by inference, compute and agent use. These terminal-and-agents prices do not describe it.
  • Unknown after the 2026-11-21 inherited-lead recheck of first-party docs, releases and public code: currency, seats, seat_minimum, workspace_fees, trial, overages, taxes. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Currency [unknown] Not established for currency in the named first-party source pass. Product access and scenario tests were not run.
  • Interval [supported] Build is $20/month monthly or $18/month annually. Max is $200 monthly or $180/month annually. Business is $50/user/month monthly or $45 annually, checked 7 November 2026. Sources: warp-oz:nov07-pricing.
  • Seats [unknown] Not established for seats in the named first-party source pass. Product access and scenario tests were not run.
  • Seat minimum [unknown] Not established for seat minimum in the named first-party source pass. Product access and scenario tests were not run.
  • Workspace fees [unknown] Not established for workspace fees in the named first-party source pass. Product access and scenario tests were not run.
  • Included usage [supported] Build includes $20 agent usage monthly; Max includes $200; Business includes $20 per seat. Compute and platform charges require separate checks. Sources: warp-oz:nov07-pricing.
  • Credits [supported] Inference, compute and platform usage are cost components drawn from one balance of included and purchased usage, not separate credit buckets; factory platform charges draw from shared team funding. Sources: warp-oz:b07-platform-usage.
  • Trial [unknown] Not established for trial in the named first-party source pass. Product access and scenario tests were not run.
  • Overages [unknown] Not established for overages in the named first-party source pass. Product access and scenario tests were not run.
  • Taxes [unknown] Not established for taxes in the named first-party source pass. Product access and scenario tests were not run.
  • Model cost [supported] Customer-supplied inference is billed by the external provider rather than included in Warp's summaries. Sources: warp-oz:nov07-harnesses.
  • Compute cost [supported] Warp-hosted cloud compute is a separate component; self-hosted workers avoid that component but still incur cloud platform usage. Sources: warp-oz:nov07-platform-billing.

Sources: warp-oz:nov07-pricing, warp-oz:nov07-platform-billing, warp-oz:nov07-harnesses, warp-oz:b07-platform-usage

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Agent cross-checked partial

Warp Factories is labeled Early Access in the current documentation navigation; standalone cloud-agent availability is separate. Vendor terms offer email/chat support during Pacific business hours excluding weekends/US federal holidays. Terms state reasonable efforts to respond within one business day, rather than an unconditional response SLA.

Scope
Surfaces: Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: access_restrictions, release_activity, status_history, deprecation, export_options. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Release stage [supported] Warp Factories is labeled Early Access in the current documentation navigation; standalone cloud-agent availability is separate. Sources: warp-oz:nov07-factories.
  • Access restrictions [unknown] Not established for access restrictions in the named first-party source pass. Product access and scenario tests were not run.
  • Support [supported] Vendor terms offer email/chat support during Pacific business hours excluding weekends/US federal holidays. Sources: warp-oz:gap07-license.
  • Response commitments [supported] Terms state reasonable efforts to respond within one business day, rather than an unconditional response SLA. Sources: warp-oz:gap07-license.
  • Release activity [unknown] Not established for release activity in the named first-party source pass. Product access and scenario tests were not run.
  • Status history [unknown] Not established for status history in the named first-party source pass. Product access and scenario tests were not run.
  • Deprecation [unknown] Not established for deprecation in the named first-party source pass. Product access and scenario tests were not run.
  • Export options [unknown] Not established for export options in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-factories, warp-oz:gap07-license

Agent cross-checked partial

Warp states SOC2 TypeII certification. Vendor scope lists Security, Availability, Confidentiality and Processing Integrity. Enterprise report access requires a request through the Trust Center/account team. Vendor documentation was checked on 2026-11-07; the underlying audit report was not inspected. Vendor assurance statement only; audit issuer and period remain unverified.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app, Warp Factories early access · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: iso_scope, iso_issuer, iso_validity, soc2_period. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Iso scope [unknown] Not established for iso scope in the named first-party source pass. Product access and scenario tests were not run.
  • Iso issuer [unknown] Not established for iso issuer in the named first-party source pass. Product access and scenario tests were not run.
  • Iso validity [unknown] Not established for iso validity in the named first-party source pass. Product access and scenario tests were not run.
  • Soc2 type [supported] Warp states SOC2 TypeII certification. Sources: warp-oz:gap07-trust.
  • Soc2 scope [supported] Vendor scope lists Security, Availability, Confidentiality and Processing Integrity. Sources: warp-oz:gap07-trust.
  • Soc2 period [unknown] Not established for soc2 period in the named first-party source pass. Product access and scenario tests were not run.
  • Report access [supported] Enterprise report access requires a request through the Trust Center/account team. Sources: warp-oz:gap07-trust.
  • Verification date [supported] Vendor documentation was checked on 2026-11-07; the underlying audit report was not inspected. Sources: warp-oz:gap07-trust.
  • Evidence status [supported] Vendor assurance statement only; audit issuer and period remain unverified. Sources: warp-oz:gap07-trust.

Sources: warp-oz:gap07-trust

Agent cross-checked partial

Free is $0/month with core terminal features, limited cloud access and limited conversation storage; additional usage may be purchased.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Useful free tier and evaluation access: first-party sources in this pass did not establish trial, credits_trial, self_host_cost, paid_only, early_access, free_scenarios, card_required, usage_caps, paid_evaluation. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
  • Warp Factories lists its own $0 pay-as-you-go plan with usage at 20% above API rates; this answer does not describe it.
10 atomic answers
  • Ongoing free [supported] Free is $0/month with core terminal features, limited cloud access and limited conversation storage; additional usage may be purchased. Sources: warp-oz:nov07-pricing.
  • Trial [unknown] Not established for trial in the named first-party source pass. Product access and scenario tests were not run.
  • Credits trial [unknown] Not established for credits trial in the named first-party source pass. Product access and scenario tests were not run.
  • Self host cost [unknown] Not established for self host cost in the named first-party source pass. Product access and scenario tests were not run.
  • Paid only [unknown] Not established for paid only in the named first-party source pass. Product access and scenario tests were not run.
  • Early access [unknown] Not established for early access in the named first-party source pass. Product access and scenario tests were not run.
  • Free scenarios [unknown] Not established for free scenarios in the named first-party source pass. Product access and scenario tests were not run.
  • Card required [unknown] Not established for card required in the named first-party source pass. Product access and scenario tests were not run.
  • Usage caps [unknown] Not established for usage caps in the named first-party source pass. Product access and scenario tests were not run.
  • Paid evaluation [unknown] Not established for paid evaluation in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-pricing

Agent cross-checked partial

Eligible dollar-billed accounts pay $3/agent-hour or $0.05/billable minute. Warp Agent meters response generation; Claude Code and Codex meter active runtime including commands. Enterprise follows contract. Enterprise has custom prices and shared usage pools.

Scope
Surfaces: Warp Automation Platform / Oz cloud runs, Warp Factories early access, Oz web app · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Pricing transparency: first-party sources in this pass did not establish included_limits, overages, compute_markup, model_markup, minimum_commitment, cancellation, transparency_classification. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
9 atomic answers
  • Units [supported] Eligible dollar-billed accounts pay $3/agent-hour or $0.05/billable minute. Warp Agent meters response generation; Claude Code and Codex meter active runtime including commands. Enterprise follows contract. Sources: warp-oz:nov07-platform-billing.
  • Included limits [unknown] Not established for included limits in the named first-party source pass. Product access and scenario tests were not run.
  • Overages [unknown] Not established for overages in the named first-party source pass. Product access and scenario tests were not run.
  • Compute markup [unknown] Not established for compute markup in the named first-party source pass. Product access and scenario tests were not run.
  • Model markup [unknown] Not established for model markup in the named first-party source pass. Product access and scenario tests were not run.
  • Minimum commitment [unknown] Not established for minimum commitment in the named first-party source pass. Product access and scenario tests were not run.
  • Cancellation [unknown] Not established for cancellation in the named first-party source pass. Product access and scenario tests were not run.
  • Sales only unknowns [supported] Enterprise has custom prices and shared usage pools. Sources: warp-oz:nov07-pricing.
  • Transparency classification [unknown] Not established for transparency classification in the named first-party source pass. Product access and scenario tests were not run.

Sources: warp-oz:nov07-pricing, warp-oz:nov07-platform-billing

Sources

warp-oz:nov07-platform

Cloud agents

Cloud-agent documentation separates factories from standalone runs and lists local/cloud handoff, API access and configured worker execution.

Kind
documented
Locator
Workflows; API access; configuration
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-web

Oz web app for cloud agents

Browser/mobile app creates runs, agents, skills, schedules, environments and integrations. Runs include status, creator, source, outputs, cost and parent/child inspection.

Kind
documented
Locator
Mobile; Runs; Filters; Onboarding
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-cli

Oz CLI reference

Oz CLI runs native agents in cloud or on the current host and manages runs, schedules, environments, MCP, skills, secrets and identity using Warp authentication.

Kind
documented
Locator
Run; API key; Schedules; Agent configs
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-desktop

Warp Terminal

Warp app has macOS, Windows and Linux downloads and is a client for standalone cloud runs.

Kind
documented
Locator
Download choices; Cloud agents
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-desktop-cloud

Cloud agents quickstart

The desktop Warp app opens standalone cloud-agent conversations, configures environments and inspects retained run records.

Kind
documented
Locator
Prerequisites; cloud-agent; Run detail
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-factory-name

Warp Factories: Infrastructure for Software Factories

The current factory offering is branded Warp Factories and described as infrastructure for software factories. Current page still offers request early access. This does not establish that all standalone Oz workflows were renamed or discontinued.

Kind
documented
Locator
Product name; introductory description; early-access CTA
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-oz-transition

Transitioning from Oz to Warp Factories

Factories is the web experience for team workflows; existing standalone workflows continue using Oz web app, Oz CLI, SDKs and API references. New software factories use platform.warp.dev. The guide describes adoption/migration rather than an explicit complete product rename.

Kind
documented
Locator
Opening paragraph; Current status table; Existing web app workflows
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-factory-offsite

Build the factory. Let it run. Go kayaking.

The October 3 vendor post uses Warp Factories and describes transition from early access toward general availability. A statement of transition is not an exact GA launch date or proof that current access gates ended.

Kind
documented
Locator
Reliability. Cost. Latency.
Source date
2026-10-03
Retrieved
2026-11-07
warp-oz:gap07-oz-name

Oz Cloud Agent Platform: Every agent at your command

The /oz page retains the Oz Cloud Agent Platform title and links standalone automation to oz.warp.dev, while global navigation promotes Warp Factories. This retained standalone naming limits any inferred blanket Oz rename.

Kind
documented
Locator
Current page title; automation/sign-in links
Source date
Not stated
Retrieved
2026-11-07
warp-oz:nov07-harnesses

Agent harnesses

Factories and standalone runs support Warp Agent, Claude Code and Codex. The current page makes plan eligibility conditional instead of a fixed Build minimum.

Kind
documented
Locator
Harness identifiers; plan requirements; billing
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-orchestration

Multi-agent orchestration

Native parent/child orchestration is one level deep, supports mixed Warp/Claude/Codex harnesses, durable per-agent inboxes, lifecycle events and wake-on-followup. Cloud-local shares filesystem; other cloud children have their own environments.

Kind
documented
Locator
Parent/child; Messaging; Mode boundaries
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-auth

Configuring harness authentication

Managed-secret Claude Code/Codex cloud setup uses funded provider API credentials. Local Codex ChatGPT sign-in is explicitly different. Factory auth secrets must be team scoped; ad hoc personal runs may use personal secrets.

Kind
documented
Locator
Cloud credential paths; Scope
Source date
Not stated
Retrieved
2026-11-07
warp-oz:nov07-platform-billing

Platform usage

Cloud runs incur platform usage even on self-hosted workers. Eligible dollar-billed plans charge $3 per agent-hour; inference and hosted compute are separate.

Kind
documented
Locator
How platform usage is measured; when charges apply
Source date
Not stated
Retrieved
2026-11-07
warp-oz:b07-platform-usage

Platform usage

Inference billed through Warp, Warp-hosted compute and platform usage ($3 per agent hour on Free, Build, Max and Business for dollar-billed accounts) are cost components drawn from one balance, not independent allowances. Customer-supplied inference is billed by the provider. Factory runs incur platform charges on Start, Scale and Enterprise; factory charges draw from shared team or workspace funding.

Kind
documented
Locator
How platform usage is measured; Inference, compute, and platform usage; When platform charges apply; Tracking platform usage
Source date
Not stated
Retrieved
2026-11-21
warp-oz:b07-harnesses

Harnesses

With provider credentials the inference provider bills the customer; Warp charges for Warp-hosted compute and platform usage per plan or contract.

Kind
documented
Locator
Billing; Plan requirements
Source date
Not stated
Retrieved
2026-11-21
warp-oz:ade158-platform-usage

Warp platform usage

The dollar rate of $3 per agent hour is scoped to Terminal/local-agent Free, Build, Max and Business accounts. Factory charges apply on Start, Scale and Enterprise and use shared funding; this page states no Factory rate.

Kind
documented
Locator
How platform usage is measured; Warp Terminal and local agents; Warp Factories; Tracking platform usage
Source date
2026-11-19
Retrieved
2026-11-22
warp-oz:gap07-unmanaged

Unmanaged execution

oz agent run executes on the current CI, Kubernetes, VM or dev host on macOS/Linux/Windows. Repeatable --share flags grant team/user view or edit access.

Kind
documented
Locator
Host; Setup; Sharing
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-environment

Configuring cloud agent environments

Standalone environments configure multiple authorized GitHub repos, Docker images and setup commands. Guided setup recommends tooling. Runs default non-root when possible but may retain root if non-root setup fails.

Kind
documented
Locator
Prerequisites; Setup; Users
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-schedule-details

Scheduled Agents

Scheduled agents execute server-side cron workflows, each with fresh context. CLI/web edit, pause and delete controls are documented; no environment yields a bare sandbox. CLI-created schedules run as creator unless changed in web app.

Kind
documented
Locator
Cron; Isolated runs; Update; Pause
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-factory-mcp

Factory MCP for coding agents

Hosted Factory MCP can send/list/search/get tasks, retrieve conversation, message foreman and hand work back with task identity. OAuth or agent key has full principal permissions, no read-only/per-factory scope.

Kind
documented
Locator
Task CRUD; Auth; Handoff
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-mcp

MCP servers for cloud agents

Cloud agents use stdio or remote MCP plus managed OAuth installations; factory-wide versus per-agent grants are separate. Connected Slack/Linear/Jira integration tools need no separate MCP installation.

Kind
documented
Locator
Transports; Scope; Integration tools
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-factory-flow

How Warp Factories work

Factory work items retain identity across triage/spec/implementation/review. Foreman dispatches specialized agents, returns revisions to existing conversations and hands PRs to humans. Spec gates are instruction policy and merges require repository controls.

Kind
documented
Locator
Work identity; Stages; Human control
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-cloud-rules

Agent harnesses

Factory and standalone cloud runs use skills and project Rules, with each harness retaining its own tool/context behavior. Config and auth are selected per factory agent or ad hoc run.

Kind
documented
Locator
Shared capabilities; Instructions
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-dashboard

Factory dashboard

Dashboard exposes run timeline/cost/subagents, PR cycle time and estimated cost per PR including children. Warp-managed definition edits validate and commit; agent-proposed definitions use spec-review inbox with request-changes or approve/merge.

Kind
documented
Locator
Metrics; Runs; Definitions
Source date
Not stated
Retrieved
2026-11-07
warp-oz:nov07-sharing

Cloud agent session sharing

Authorized users can inspect and follow up remote runs while the VM remains active; after shutdown a conversation can be forked locally.

Kind
documented
Locator
What it enables; inactive sessions; fork to local
Source date
Not stated
Retrieved
2026-11-07
warp-oz:nov07-inbox

Factory inbox

A personal queue gathers questions, spec/PR reviews, blocked and failed items for tasks the user started.

Kind
documented
Locator
What appears; reviewing your inbox
Source date
Not stated
Retrieved
2026-11-07
warp-oz:b07-home

Reviewing items on Home

Home (redirect target of factory-inbox) is personal: its run views show factory runs you started, and Waiting on you shows items directed to you, including GitHub PR reviews requested from you on others' work. Status filters Active, Complete, Blocked and Failed.

Kind
documented
Locator
What appears in Waiting on you; Finding other runs
Source date
Not stated
Retrieved
2026-11-21
warp-oz:b07-factories

Warp Factories

Every worker run is a cloud agent run; the factory dashboard shows PR activity, autonomy, cycle time and cost.

Kind
documented
Locator
Execution; Evaluate and improve
Source date
Not stated
Retrieved
2026-11-21
warp-oz:b07-dashboard

Factory dashboard

Dashboard shows autonomy, PR cycle time, cost per PR, opened versus merged PRs and a runs breakdown for a date range; the team-wide Runs page lists runs you can access with child runs grouped under parents, timelines and cost.

Kind
documented
Locator
Read metrics on the Dashboard page; Inspect runs
Source date
Not stated
Retrieved
2026-11-21
warp-oz:ade158-home

Reviewing items on Home

Home run views show runs started by the current user. Waiting on you also includes PR reviews requested from that person on someone else’s work.

Kind
documented
Locator
What appears in Waiting on you; Finding other runs
Source date
2026-11-19
Retrieved
2026-11-22
warp-oz:gap07-workers

Self-hosting overview

Enterprise workers support Docker/Kubernetes/Direct/Command execution on customer compute. Warp retains the control plane, operational metadata and billing. Transcript/artifact buckets are independently configurable.

Kind
documented
Locator
Backends; Architecture; Data; Routing
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-cloud-session

Cloud agent session sharing

Cloud sessions expose commands, logs, plans and artifacts, permit followups while the environment is active, and fork conversations locally after shutdown; code branches may require manual clone.

Kind
documented
Locator
Inspect; Followup; Expiry; Fork
Source date
Not stated
Retrieved
2026-11-07
warp-oz:nov13-cloud-lifetime

Handoff from local to cloud

Local-to-cloud handoff transfers an active conversation and workspace snapshot so a long-running task can continue without keeping the laptop awake.

Kind
documented
Locator
When to use handoff
Source date
Not stated
Retrieved
2026-11-13
warp-oz:gap07-worktrees

Direct backend Git worktrees

Direct tasks can use per-run worktrees and branches through configured setup/teardown hooks. These share host processes/network/Git metadata and are not OS sandboxes.

Kind
documented
Locator
Lifecycle; Caution
Source date
Not stated
Retrieved
2026-11-07
warp-oz:nov13-cloud-vm

Cloud agent session sharing

Shared cloud agent runs execute on remote virtual machines, whose code/config changes, commands, logs and outputs can be reviewed through Warp or the browser. Idle environments can shut down.

Kind
documented
Locator
Overview; inspect session; inactive environments
Source date
Not stated
Retrieved
2026-11-13
warp-oz:gap07-worker-controls

Self-hosted worker reference

max-concurrent-tasks defaults unlimited and queues excess work when capped. One-shot Direct forces one task; completion-idle settings and Kubernetes resource/timeouts are configurable.

Kind
documented
Locator
Concurrency; Timeout; Resource flags
Source date
Not stated
Retrieved
2026-11-07
warp-oz:nov07-pricing

Warp pricing

Free, Build, Max, Business and custom Enterprise plans distinguish included usage, collaboration and customer-supplied inference.

Kind
documented
Locator
Warp Terminal and agents plans, checked 7 November 2026
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-roles

Managing factory permissions

Enterprise Factory user/Editor roles control run versus configuration rights, with Admin management and factory-specific overrides. Non-Enterprise members are Editors; role does not grant merge or spec approval authority.

Kind
documented
Locator
Role matrix; Enterprise; Merge authority
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-inbox

Factory inbox

Personal Inbox includes questions, spec approvals, PR reviews and blocked/failed items only for tasks started by that person. Items auto-clear or can be resolved/undone and filtered.

Kind
documented
Locator
Items; Scope; Actions
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-license

Warp product and services license agreement

Hosted Warp products use a limited proprietary service license with redistribution/reverse-engineering restrictions. Vendor support uses Pacific business hours with reasonable one-business-day response efforts.

Kind
documented
Locator
Sections 2.1–2.3; 1.3
Source date
2025-10-07
Retrieved
2026-11-07
warp-oz:nov07-factories

Warp Factories overview

The official docs label Factories Early Access, separate from standalone cloud-agent availability.

Kind
documented
Locator
Early Access; overview
Source date
Not stated
Retrieved
2026-11-07
warp-oz:gap07-trust

Warp Trust Center

Vendor states SOC2 TypeII and provides Enterprise reports on request. Scope lists security, availability, confidentiality and processing integrity; no report was inspected.

Kind
documented
Locator
SOC2; Access; Provider ZDR
Source date
Not stated
Retrieved
2026-11-07

Comparisons with Warp Factories / Oz

Compare Warp Factories / Oz with any other product on adecomparison.com.