Merge branch 'main' into oz/docs/snapshot-declarations

hongyi-chen · web-flow · commit 34990aa09699 · 2026-05-19T16:43:54.000-07:00
diff --git a/src/content/docs/agent-platform/capabilities/full-terminal-use.mdx b/src/content/docs/agent-platform/capabilities/full-terminal-use.mdx
@@ -107,14 +107,14 @@ The behavior differs based on where you start the long-running command:
     1. Run an interactive command (e.g., `python`, `psql`)
     2. Press `⌘↩` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux), or use `⌘I` (macOS) / `Ctrl+I` (Windows/Linux), to tag in the agent
     3. The input switches to Agent Mode with full controls
-    4. When you exit, an agent conversation block appears in your terminal blocklist
+    4. When you exit, an agent conversation block appears in your terminal block list
     5. Click the block to reopen the full conversation with your LRC interaction context
   </TabItem>
   <TabItem label="From agent view">
     1. The agent runs an interactive command as part of your conversation
     2. Use `⌘↩` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux) to tag in if the agent isn't already interacting
     3. The UI stays the same since you're already in agent view
-    4. When you exit, the interaction remains part of your conversation. No separate block is created in the terminal blocklist
+    4. When you exit, the interaction remains part of your conversation. No separate block is created in the terminal block list
     5. Commands run in agent view are automatically included as context
   </TabItem>
 </Tabs>
diff --git a/src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx b/src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx
@@ -1,5 +1,5 @@
 ---
-title: Deployment Patterns
+title: Deployment patterns
 description: >-
   Common architectures for deploying cloud agents, including CLI-only,
   Oz-hosted, and self-hosted execution patterns.
diff --git a/src/content/docs/agent-platform/cloud-agents/faqs.mdx b/src/content/docs/agent-platform/cloud-agents/faqs.mdx
@@ -57,7 +57,7 @@ Yes. Cloud agent runs execute in a full Linux environment and behave like a loca
 
 The cloud agents platform supports self-hosting the **agent sandbox** (the execution environment) on your own infrastructure. The **control plane**—which handles orchestration, tracking, and auditability—remains Warp-managed and is not self-hosted.
 
-Self-hosted execution is available on **Enterprise** plans. See [Self-Hosting](/agent-platform/cloud-agents/self-hosting/) and [Deployment Patterns](/agent-platform/cloud-agents/deployment-patterns/) for details.
+Self-hosted execution is available on **Enterprise** plans. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) and [Deployment patterns](/agent-platform/cloud-agents/deployment-patterns/) for details.
 
 :::note
 [Bring Your Own Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) does not apply to cloud agents. BYOK keys are stored locally on your device and cannot be passed to cloud-hosted or self-hosted agent runs. All cloud agent runs consume [Warp credits](/support-and-community/plans-and-billing/credits/).
@@ -203,7 +203,7 @@ With self-hosting, repositories are cloned and stored only on your infrastructur
 * **Execution plane (your infrastructure)** — Repository clones, build artifacts, runtime secrets, and container filesystem state stay on the machines you control.
 * **Control plane (Warp-hosted)** — Session transcripts (which include code context from agent interactions), orchestration metadata, and LLM inference route through Warp's backend under [Zero Data Retention (ZDR)](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr) agreements. Warp does not persistently store your source code or use it for model training.
 
-See [Self-Hosting](/agent-platform/cloud-agents/self-hosting/) for deployment options and [Security Overview](/enterprise/security-and-compliance/security-overview/) for full details.
+See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) for deployment options and [Security Overview](/enterprise/security-and-compliance/security-overview/) for full details.
 
 ### Can I use `oz agent run` in CI or existing runners?
 
@@ -226,7 +226,7 @@ Yes. LLM inference routes through Warp's backend, which has [Zero Data Retention
 The [unmanaged architecture](/agent-platform/cloud-agents/self-hosting/unmanaged/) is well-suited for large monorepos because agents run directly in your pre-provisioned environment — there is no Docker image build or repo cloning step. For the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture), the Docker backend supports volume mounts (`-v` flag) to mount a pre-existing repo checkout from the host into task containers. With the Kubernetes backend, use `pod_template` to configure persistent volume claims or pre-populated storage for the same purpose.
 
 :::note
-The managed architecture supports three execution backends: **Docker** (default), **Kubernetes**, and **Direct** (no container runtime). The Kubernetes backend runs each task as a Kubernetes Job and includes a Helm chart for deployment. See [Self-Hosting](/agent-platform/cloud-agents/self-hosting/#choosing-a-managed-backend) for details on choosing a backend.
+The managed architecture supports three execution backends: **Docker** (default), **Kubernetes**, and **Direct** (no container runtime). The Kubernetes backend runs each task as a Kubernetes Job and includes a Helm chart for deployment. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/#choosing-a-managed-backend) for details on choosing a backend.
 :::
 
 ### Do Kubernetes pods provide enough sandboxing for self-hosted agents?
diff --git a/src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.mdx b/src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.mdx
@@ -1,5 +1,5 @@
 ---
-title: Managing Cloud Agents
+title: Managing cloud agents
 description: >-
   Monitor and manage cloud agent activity across your team with Warp's
   centralized management view, including filtering, status tracking, and
diff --git a/src/content/docs/agent-platform/cloud-agents/overview.mdx b/src/content/docs/agent-platform/cloud-agents/overview.mdx
@@ -57,7 +57,7 @@ Cloud agents run on the [Oz Platform](/agent-platform/cloud-agents/platform/), w
 
 The exact way tasks are triggered and executed depends on your deployment model (for example CLI-only, Warp-hosted orchestration, or self-hosted execution). Those options are covered in the [Deployment Patterns](/agent-platform/cloud-agents/deployment-patterns/) pages.
 
-For teams that need execution to stay within their network boundary, self-hosting supports two architectures: a **managed** worker daemon that lets Oz orchestrate agents in Docker containers on your machines, and an **unmanaged** mode where you run `oz agent run` directly in your CI, Kubernetes, or dev environment. See [Self-Hosting](/agent-platform/cloud-agents/self-hosting/) for details.
+For teams that need execution to stay within their network boundary, self-hosting supports two architectures: a **managed** worker daemon that lets Oz orchestrate agents in Docker containers on your machines, and an **unmanaged** mode where you run `oz agent run` directly in your CI, Kubernetes, or dev environment. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) for details.
 
 ### What you get by default
 
@@ -146,6 +146,7 @@ If your credit balance reaches zero, cloud agent runs will not be able to execut
 * [Oz Platform](/agent-platform/cloud-agents/platform/) — CLI, Oz API/SDK, orchestration, tasks, environments, hosts, integrations, and more.
 * [Harnesses](/agent-platform/cloud-agents/harnesses/) — pick between Warp Agent, Claude Code, and Codex for any cloud agent run.
 * [Agent identities](/agent-platform/cloud-agents/agents/) — team-scoped bot accounts that own and execute cloud agent runs.
+* [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) — coordinate a parent agent and its child agents across local and cloud runs to build supervisor/worker, fan-out, critic, DAG, and swarm workflows.
 * [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/) — run agents based on reusable skill definitions from the CLI, web app, API, or on a schedule.
 * [Oz CLI](/reference/cli/) — shows how to run agents in non-interactive mode from CI, scripts, or remote machines, including auth and common commands.
 * [Environments](/agent-platform/cloud-agents/environments/) — explains how environments provide the runtime context (repo, image, startup commands) for agent tasks.
diff --git a/src/content/docs/agent-platform/cloud-agents/platform.mdx b/src/content/docs/agent-platform/cloud-agents/platform.mdx
@@ -185,7 +185,7 @@ With self-hosting:
 * This is used when teams want code and execution to remain on their own systems rather than being cloned or executed in Warp's cloud.
 
 :::note
-**Enterprise feature**: Self-hosted execution requires an Enterprise plan. See [Self-Hosting](/agent-platform/cloud-agents/self-hosting/) for setup instructions.
+**Enterprise feature**: Self-hosted execution requires an Enterprise plan. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) for setup instructions.
 :::
 
 ---
diff --git a/src/content/docs/agent-platform/cloud-agents/warp-hosting.mdx b/src/content/docs/agent-platform/cloud-agents/warp-hosting.mdx
@@ -1,12 +1,12 @@
 ---
 title: Warp-hosted agents
 description: >-
-  Run Oz cloud agents on Warp's infrastructure. Warp handles scaling, isolation, and performance for agent execution.
+  Run cloud agents on Warp's infrastructure. Warp handles scaling, isolation, and performance for agent execution.
 sidebar:
   label: "Warp-hosted agents"
 ---
 
-Warp's managed infrastructure lets your team easily run Oz cloud agent workloads in fast and secure sandboxes.
+Warp's managed infrastructure lets your team run cloud agent workloads in fast, secure sandboxes.
 
 Use Warp-hosted agents to quickly get started with Oz, without needing to configure compute resources or maintain services. 
 
diff --git a/src/content/docs/agent-platform/local-agents/agent-context/blocks-as-context.mdx b/src/content/docs/agent-platform/local-agents/agent-context/blocks-as-context.mdx
@@ -12,7 +12,7 @@ Attach terminal output blocks to your agent prompts so the agent can understand
 
 Warp’s Agent can use blocks from your Agent conversations as context to better understand your queries and generate more relevant responses.
 
-You can attach a block directly from the terminal blocklist by clicking the AI sparkles icon on it and selecting “Attach as context.”
+You can attach a block directly from the terminal block list by clicking the AI sparkles icon on it and selecting “Attach as context.”
 
 <figure>
 ![From a block of output, attach the block and ask Agent Mode to remove all untracked files.](../../../../../assets/agent-platform/remove_all_untracked_files.png)
@@ -77,8 +77,8 @@ The most common use case is to ask the AI to fix an error. You can attach the er
 
 Blocks in Warp belong to either the terminal view or a specific agent conversation:
 
-* **Terminal blocks** - Commands you run directly in the terminal. These always appear in your terminal blocklist and can be attached as context to multiple conversations.
-* **Agent conversation blocks** - Commands executed within an agent conversation (either by you or the agent). These only appear within that specific conversation and don't clutter your terminal blocklist.
+* **Terminal blocks** - Commands you run directly in the terminal. These always appear in your terminal block list and can be attached as context to multiple conversations.
+* **Agent conversation blocks** - Commands executed within an agent conversation (either by you or the agent). These only appear within that specific conversation and don't clutter your terminal block list.
 
 This separation keeps your terminal view clean while preserving full context within each conversation.
 
diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/conversation-forking.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/conversation-forking.mdx
@@ -41,7 +41,7 @@ You can also access this conversation view from the conversation chip in the cur
 
 #### **2. From the footer of the most recent AI response block**
 
-In any conversation in the blocklist, click the **fork button** in the footer of the most recent AI block. A new conversation opens in a separate pane with the full context of the original.
+In any conversation in the block list, click the **fork button** in the footer of the most recent AI block. A new conversation opens in a separate pane with the full context of the original.
 
 ![Fork conversation button in the footer of the most recent agent response block](../../../../../assets/agent-platform/conversation-forking-footer.png)
 
diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/index.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/index.mdx
@@ -142,9 +142,9 @@ If you switch models during a conversation, the context usage indicator updates
 
 Warp automatically detects when your query has shifted to a new topic. When this happens, it suggests starting a new conversation instead of continuing in the same context.
 
-These options appear in the blocklist, where you can decide whether to branch off into a new conversation or keep going with the current one.
+These options appear in the block list, where you can decide whether to branch off into a new conversation or keep going with the current one.
 
-![Suggestion in the blocklist to start a new conversation when Warp detects a topic shift.](../../../../../assets/agent-platform/conversation-segmentation.png)
+![Suggestion in the block list to start a new conversation when Warp detects a topic shift.](../../../../../assets/agent-platform/conversation-segmentation.png)
 
 You can also create a new conversation manually at any time by using the keyboard shortcut, opening a new tab, or opening a new pane.
 
diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx
@@ -98,14 +98,14 @@ Agent Mode-specific items include the model selector, autodetection toggle, Cont
 
 Blocks in Warp belong to either the terminal view or a specific agent conversation:
 
-* **Terminal blocks** - Commands you run directly in the terminal always appear in your terminal blocklist and can be attached as context to any conversation.
-* **Agent conversation blocks** - Commands executed within an agent conversation (either by you or the agent) only appear within that specific conversation and don't appear in the terminal blocklist.
+* **Terminal blocks** - Commands you run directly in the terminal always appear in your terminal block list and can be attached as context to any conversation.
+* **Agent conversation blocks** - Commands executed within an agent conversation (either by you or the agent) only appear within that specific conversation and don't appear in the terminal block list.
 
 In agent conversations, context is managed automatically, with optional manual attachment from terminal view:
 
 * **Automatic context** - Commands executed within an agent conversation are included as context for subsequent prompts.
 * **Manual attachment** - You can attach terminal blocks to bring in outputs from outside the conversation.
-* **Conversation scope** - Agent conversation blocks stay scoped to that conversation, while terminal blocks remain in the terminal blocklist.
+* **Conversation scope** - Agent conversation blocks stay scoped to that conversation, while terminal blocks remain in the terminal block list.
 
 This separation keeps your terminal view clean while preserving full context within each conversation. For shortcuts, pending vs. attached context, and block selection behavior, see [Blocks as Context](/agent-platform/local-agents/agent-context/blocks-as-context/).
 
diff --git a/src/content/docs/code/overview.mdx b/src/content/docs/code/overview.mdx
@@ -6,7 +6,7 @@ description: >-
 ---
 import VideoEmbed from '@components/VideoEmbed.astro';
 
-Warp's coding features help you go from prompt to production. They combine a dedicated coding agent — consistently ranked among the top on SWE-bench Verified — with a native code editor, inline diff review, codebase context, and project-level rules for accurate, context-aware code generation.
+Warp's coding features help you go from prompt to production. They combine a dedicated coding agent — consistently ranked among the top on SWE-bench Verified — with a native code editor, inline diff review, Codebase Context, and project-level rules for accurate, context-aware code generation.
 
 :::note
 On macOS and Linux SSH sessions, Warp's [SSH extension](/terminal/warpify/ssh/#installing-the-ssh-extension) brings the file tree, native file reads, and native code diffs to remote hosts. See [Feature support over SSH](/code/ssh-feature-support/) for the current support matrix.
diff --git a/src/content/docs/enterprise/enterprise-features/analytics-api.mdx b/src/content/docs/enterprise/enterprise-features/analytics-api.mdx
@@ -136,7 +136,7 @@ In the grouped response, every leaf array is the same length as `period_list`, a
 
 ### `GET /api/v1/enterprises/analytics/users`
 
-Returns per-user aggregated usage, split into `local` (Warp app) and `cloud` (Oz cloud agents) sections. Results are paginated.
+Returns per-user aggregated usage, split into `local` (Warp app) and `cloud` (cloud agents) sections. Results are paginated.
 
 **Query parameters:**
 
diff --git a/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx b/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx
@@ -163,7 +163,7 @@ Once your team is set up:
 * **Agent Profiles** - Configure default [Agent Profiles](/agent-platform/capabilities/agent-profiles-permissions/) for different types of work to give teams appropriate autonomy and control
 * **BYOLLM** - Set up [Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/) to route inference through your cloud infrastructure for data locality and cost control
 * **Monitor usage** - Review usage analytics in the Admin Panel to track adoption and measure engineering productivity gains
-* **Self-hosting** - Run agents on your own infrastructure to control where agents run and keep repository clones on your own machines. See [Self-Hosting](/agent-platform/cloud-agents/self-hosting/) for setup instructions
+* **Self-hosting** - Run agents on your own infrastructure to control where agents run and keep repository clones on your own machines. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) for setup instructions
 
 ## Troubleshooting
 
diff --git a/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx b/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx
@@ -49,7 +49,7 @@ In the demo, we run three parallel workflows:
        Analyze how many pull requests a team member has assigned.
 
            ```
-       Use the Github CLI tool to summarize all open PRs for review that are assigned to user. I'd like to see who is the author of the PR, when was it opened, how long has it been open for, which repo is it in, are there open an dunaddressed commens on it, and is it ready for review?
+       Use the GitHub CLI tool to summarize all open PRs for review that are assigned to user. I'd like to see who is the author of the PR, when was it opened, how long has it been open for, which repo is it in, are there open an dunaddressed commens on it, and is it ready for review?
        ```
        </TabItem>
      <TabItem label="Log Analysis">
diff --git a/src/content/docs/guides/agent-workflows/warp-for-product-managers.mdx b/src/content/docs/guides/agent-workflows/warp-for-product-managers.mdx
@@ -1,5 +1,5 @@
 ---
-title: "5 AI agent workflows for product managers"
+title: "5 agent workflows for product managers"
 description: >-
   Five agent workflows that automate status updates, documentation, Slack search,
   and meeting prep for product managers.
diff --git a/src/content/docs/guides/build-an-app-in-warp/building-a-real-time-chat-app-github-mcp-railway.mdx b/src/content/docs/guides/build-an-app-in-warp/building-a-real-time-chat-app-github-mcp-railway.mdx
@@ -1,5 +1,5 @@
 ---
-title: Building a Real-time Chat App (Github MCP + Railway )
+title: Building a Real-time Chat App (GitHub MCP + Railway)
 description: >-
   Build and deploy a real-time chat app with Python, FastAPI, and JavaScript —
   from idea to production, all inside Warp.
@@ -229,6 +229,6 @@ The project: a **real-time chat application** built with **Python (FastAPI)** an
 
 ### Appendix
 
-* [Github MCP Server](https://github.com/github/github-mcp-server)
+* [GitHub MCP Server](https://github.com/github/github-mcp-server)
 * [Docker Desktop download](https://www.docker.com/products/docker-desktop/)
 * [Railway](https://railway.com/)
diff --git a/src/content/docs/guides/external-tools/github-mcp-summarizing-open-prs-and-creating-gh-issues.mdx b/src/content/docs/guides/external-tools/github-mcp-summarizing-open-prs-and-creating-gh-issues.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Github MCP: Summarizing Open PRs & Creating GH Issues"
+title: "GitHub MCP: Summarizing Open PRs & Creating GH Issues"
 description: >-
   Connect the GitHub MCP server to Warp to summarize open PRs, create issues
   from TODO comments, and automate repo management.
diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/operation-not-supported.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/operation-not-supported.mdx
@@ -55,5 +55,5 @@ This error is returned when:
 ## Related
 
 * [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — How cloud agent tasks work
-* [Self-Hosting](/agent-platform/cloud-agents/self-hosting/) — Self-hosted agent configuration
+* [Self-hosting](/agent-platform/cloud-agents/self-hosting/) — Self-hosted agent configuration
 * [Oz API & SDK](/reference/api-and-sdk/) — API reference for managing agent tasks
diff --git a/src/content/docs/reference/cli/artifacts.mdx b/src/content/docs/reference/cli/artifacts.mdx
@@ -1,7 +1,7 @@
 ---
 title: Artifacts
 description: >-
-  Get metadata for and download files produced by an Oz agent run using the
+  Get metadata for and download files produced by an agent run using the
   `oz artifact` subcommands.
 sidebar:
   label: "Artifacts"
diff --git a/src/content/docs/support-and-community/privacy-and-security/privacy.mdx b/src/content/docs/support-and-community/privacy-and-security/privacy.mdx
diff --git a/src/content/docs/support-and-community/troubleshooting-and-support/logging-out-and-uninstalling.mdx b/src/content/docs/support-and-community/troubleshooting-and-support/logging-out-and-uninstalling.mdx
diff --git a/src/content/docs/terminal/appearance/custom-themes.mdx b/src/content/docs/terminal/appearance/custom-themes.mdx
diff --git a/src/content/docs/terminal/more-features/full-screen-apps.mdx b/src/content/docs/terminal/more-features/full-screen-apps.mdx
diff --git a/src/content/docs/terminal/more-features/text-selection.mdx b/src/content/docs/terminal/more-features/text-selection.mdx
diff --git a/src/content/docs/terminal/settings/file-locations.mdx b/src/content/docs/terminal/settings/file-locations.mdx
diff --git a/src/content/docs/terminal/settings/index.mdx b/src/content/docs/terminal/settings/index.mdx
diff --git a/src/content/docs/terminal/windows/tab-configs.mdx b/src/content/docs/terminal/windows/tab-configs.mdx
diff --git a/src/sidebar.ts b/src/sidebar.ts
