May AEO docs updates

src/content/docs/agent-platform/capabilities/mcp.mdx

@@ -1,7 +1,7 @@
 ---
 title: Model Context Protocol (MCP)
 description: >-
-  Configure MCP servers in the Warp desktop app to extend local agents with
+  Configure MCP servers in the Warp app to extend local agents with
   custom tools and data sources through a standardized interface.
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
@@ -12,7 +12,7 @@ MCP servers extend Warp's [local agents](/agent-platform/local-agents/interactin
 MCP is an open source protocol. Check out the official [MCP documentation](https://modelcontextprotocol.io/introduction) for more detailed information on how this protocol is engineered.
 
 :::note
-This page covers MCP servers for local agents in the Warp desktop app. If you're using cloud agents, see [MCP Servers for cloud agents](/agent-platform/cloud-agents/mcp/).
+This page covers MCP servers for local agents in the Warp app. For help choosing between local, cloud, and shared MCP workflows, see [Connect developer tools to agents with MCP workflows](/guides/external-tools/using-mcp-servers-with-warp/). If you're using cloud agents, see [MCP Servers for cloud agents](/agent-platform/cloud-agents/mcp/).
 :::
 
 ### How to access MCP Server settings
@@ -26,7 +26,7 @@ You can navigate to the MCP servers page in any of the following ways:
 
 This will show a list of all configured MCP servers, including which are currently running. If you close Warp with an MCP server running, it will run again on next start of Warp. MCP servers that are stopped will remain so on next launch of Warp.
 
-<figure>
+<figure style={{ maxWidth: "563px" }}>
 ![MCP servers page](../../../../assets/agent-platform/mcp-servers-list.png)
 <figcaption>MCP servers page.</figcaption>
 </figure>
@@ -41,7 +41,7 @@ MCP server types you can add:
   <TabItem label="CLI Server (Command)">
     Provide a startup command. Warp will launch this command when starting up and shut it down on exit.
 
-    <figure>
+    <figure style={{ maxWidth: "375px" }}>
     ![Adding a CLI MCP Server (Command)](../../../../assets/agent-platform/mcp-servers-add-cli.png)
     <figcaption>Adding a CLI MCP Server (Command).</figcaption>
     </figure>
@@ -62,7 +62,7 @@ MCP server types you can add:
   <TabItem label="Streamable HTTP or SSE Server (URL)">
     Provide a URL where Warp can reach an already-running MCP server that supports Server-Sent Events.
 
-    <figure>
+    <figure style={{ maxWidth: "375px" }}>
     ![Adding an SSE MCP Server (URL)](../../../../assets/agent-platform/mcp-servers-add-sse.png)
     <figcaption>Adding an SSE MCP Server (URL).</figcaption>
     </figure>
@@ -134,7 +134,10 @@ To auto-spawn global servers from third-party agents:
 1. In the Warp app, go to **Settings** > **Agents** > **MCP servers**.
 2. Toggle **Auto-spawn servers from third-party agents** on.
 
+<figure style={{ maxWidth: "375px" }}>
 ![Toggle to auto-spawn global file-based MCP servers](/assets/agent-platform/file-based-mcp-setting.png)
+<figcaption>File-based MCP server settings.</figcaption>
+</figure>
 
 Project-scoped servers from any provider must be toggled on individually from the MCP servers page. These are session-scoped — after restarting Warp, toggle them on again if you still trust the repo.
 
@@ -170,7 +173,7 @@ You can rename and edit a server's name, as well as delete the server. If you ar
 
 MCP servers can be shared with your teammates by clicking the share icon. When sharing, sensitive values in the `env` configuration will be automatically scrubbed and replaced with variables.
 
-<figure>
+<figure style={{ maxWidth: "375px" }}>
 ![Sharing a MCP Server](../../../../assets/agent-platform/mcp-servers-share.png)
 <figcaption>Sharing a MCP Server.</figcaption>
 </figure>

src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx

@@ -114,6 +114,8 @@ When a task is naturally divisible, use [multi-agent orchestration](/agent-platf
 
 Use this when you need to control where agent execution happens while still using Oz orchestration and visibility. Repositories are cloned and stored only on your infrastructure; orchestration metadata, session transcripts, and LLM inference route through Warp's backend under [ZDR](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr).
 
+Think of self-hosted execution as **customer-hosted execution with Warp-hosted orchestration**, not as a fully offline agent stack. Code repositories, build artifacts, runtime secrets, and execution workspaces stay on your infrastructure. Code context can still appear in session transcripts and LLM prompts as the agent works.
+
 :::note
 **Enterprise feature**: Self-hosted execution is available exclusively to teams on an Enterprise plan.
 :::

src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx

@@ -17,7 +17,7 @@ Watch this walkthrough to see how cloud-to-cloud handoff continues a cloud agent
 Use this handoff direction when:
 
 * You want to send a follow-up to a cloud agent after its session has ended.
-* You want to continue a background cloud agent run, such as a scheduled or integration-triggered run, while preserving it as a single unit of work in the [management view](/agent-platform/cloud-agents/managing-cloud-agents/).
+* You want to continue a background cloud agent run, such as a scheduled or integration-triggered run, while preserving it as a single unit of work in the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app and the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs).
 
 ## What carries over
 
@@ -58,9 +58,9 @@ Cloud-to-cloud handoff also works for supported third-party agent runtimes, but
 
 ## Inspecting a run that's been handed off
 
-The [management view](/agent-platform/cloud-agents/managing-cloud-agents/) shows one row per run, even when the run spans multiple sessions.
+The [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app and the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs) show one row per run, even when the run spans multiple sessions.
 
-1. Open the [management view](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app or Oz web app.
+1. Open the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app or the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs).
 2. Select the handed-off run.
 3. Review the transcript. Each session appears in order, so you can see where one session ended and the next began.
 

src/content/docs/agent-platform/cloud-agents/handoff/index.mdx

@@ -50,7 +50,7 @@ Each direction has a clear motivating workflow.
 ## Related pages
 
 * [Cloud agents overview](/agent-platform/cloud-agents/overview/) - What cloud agents are, when to use them, and how they fit into the Oz Platform.
-* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Inspect handoff runs from the management view alongside local conversations.
+* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Inspect handoff runs from the Agent Management Panel in the Warp app or the Runs page in the Oz web app alongside local conversations.
 * [Viewing cloud agent runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) - Open and continue a cloud run locally with **Continue locally** or `/continue-locally`.
 * [Cloud-synced conversations](/agent-platform/local-agents/cloud-conversations/) - How conversations sync between local and cloud so handoff can find them.
 * [Environments](/agent-platform/cloud-agents/environments/) - The runtime context a cloud agent runs in after a handoff.

src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx

@@ -11,9 +11,9 @@ import VideoEmbed from '@components/VideoEmbed.astro';
 
 Oz can run third-party agent harnesses as cloud agents alongside Warp Agent, including [Claude Code](/agent-platform/cloud-agents/harnesses/claude-code/) and [Codex](/agent-platform/cloud-agents/harnesses/codex/). You choose the harness (agent runtime) that fits the task; the platform around the run stays the same.
 
-Watch this walkthrough to see how to run Warp Agent, Claude Code, or Codex as an Oz cloud agent.
+Watch this walkthrough to see how to run Warp Agent, Claude Code, or Codex as a cloud agent.
 
-<VideoEmbed url="https://www.youtube.com/watch?v=ZUYyuA5i1VU" title="How to run any agent in the cloud with Oz - Claude Code, Codex, or the Warp Agent" />
+<VideoEmbed url="https://www.youtube.com/watch?v=ZUYyuA5i1VU" title="Run any agent in the cloud with Oz - Claude Code, Codex, or Warp Agent" />
 
 ## What stays the same
 
@@ -30,7 +30,7 @@ Claude Code and Codex each call their provider directly using credentials you su
 
 ## How to switch harnesses
 
-### Warp desktop app
+### Warp app
 
 In Cloud Mode, choose a harness from the **Agent harness** dropdown above the input.
 

src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx

@@ -12,6 +12,8 @@ Run agents directly in your GitHub Actions workflows using `oz-agent-action`. Th
 **Getting started?** See the [GitHub Actions quickstart](/agent-platform/cloud-agents/integrations/quickstart-github-actions/) to set up your first workflow, or visit the [oz-agent-action repository](https://github.com/warpdotdev/oz-agent-action) for detailed setup instructions and ready-to-use workflow templates.
 :::
 
+If you're comparing GitHub Actions with schedules, Slack, Linear, the Oz CLI, or API-triggered runs, see [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/).
+
 Watch this demo to see the integration in action:
 
 <VideoEmbed url="https://www.loom.com/share/534f88b6a98e43ca9769ca09de6424b5" />

src/content/docs/agent-platform/cloud-agents/integrations/index.mdx

@@ -13,6 +13,8 @@ Warp integrations let your team trigger agents directly from the terminal, or fr
 * Run code inside your codebase in a remote environment
 * Open pull requests and perform other multi-step agent workflows on your behalf
 
+If you're deciding whether an agent should run from a schedule, Slack or Linear, GitHub Actions, the Oz CLI, or the API, see [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/).
+
 :::note
 For a full walkthrough of Warp's integrations and configurable environments, please refer to [Integration setup](/reference/cli/integration-setup/).
 :::

src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.mdx

@@ -1,39 +1,44 @@
 ---
 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
-  session inspection.
+  Monitor and manage agent activity across your team with Warp's Agent
+  Management Panel and the Oz web app's Runs page.
 sidebar:
   label: "Managing cloud agents"
 ---
 import VideoEmbed from '@components/VideoEmbed.astro';
 
-Warp provides a centralized management view where you can monitor agent activity across your account and (where applicable) your team. You can access this view in the Warp app or through the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) at [oz.warp.dev](https://oz.warp.dev), which works on mobile devices.
+Warp provides two management surfaces for tracking and observing agent activity across your account and, where applicable, your team: the **Agent Management Panel** in the Warp app and the [**Runs** page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs) at [oz.warp.dev](https://oz.warp.dev), which works on mobile devices. In Warp, open the Agent Management Panel from the Agent Management Panel button in the tab bar; in the web app, go to the Runs page.
 
-The management view is designed to answer, at a glance:
+Use these surfaces as the starting point for real-time agent observability in Warp. They help you see which agents are active, which runs are blocked or failed, where each run started, and which session link opens the prompt, plan, commands, logs, outputs, and follow-up messages behind the work.
 
-* Which agents have been running recently (and what's running right now)
-* Which runs succeeded, failed, or were canceled
-* Where an agent run was triggered from (a local agent conversation, the Oz CLI, Slack, etc.)
-* How many credits those runs consumed
+The Agent Management Panel and Oz web app Runs page are designed to answer, at a glance:
+
+* Which agents are active or have been running recently.
+* Which runs are working, blocked, failed, succeeded, or canceled.
+* Where an agent run was triggered from, such as a local agent conversation, the Oz CLI, Slack, Linear, a schedule, or the API.
+* How parent and child runs relate in orchestrated workflows.
+* Which session to open when you need prompt, plan, command, log, output, or follow-up context.
+* How many credits those runs consumed.
+
+Warp's agent observability is run- and session-oriented. It is not a replacement for full APM, OpenTelemetry, or Datadog-style tracing across arbitrary agent frameworks. Use Warp to track agent run status, trigger/source, owner, parent-child relationships, transcripts, commands, logs, outputs, and replayable session links.
 
 <VideoEmbed url="https://www.loom.com/share/679c267ddd2d44519abf79edcb1122c7" />
 
-This management view includes your **local (interactive) agents** and [cloud agent](/agent-platform/cloud-agents/overview/) runs.
+These management surfaces include your **local (interactive) agents** and [cloud agent](/agent-platform/cloud-agents/overview/) runs.
 
-<figure>
-![Warp's management view showing interactive and cloud agent runs.](../../../../assets/agent-platform/management-view-scannable-list.png)
-<figcaption>Warp's management view showing interactive and cloud agent runs.</figcaption>
+<figure style={{ maxWidth: "563px" }}>
+![Warp's Agent Management Panel showing interactive and cloud agent runs.](../../../../assets/agent-platform/management-view-scannable-list.png)
+<figcaption>Warp's Agent Management Panel showing interactive and cloud agent runs.</figcaption>
 </figure>
 
-### What appears in the management view
+### What appears in the agent management surfaces
 
-The management view includes two categories of agent activity.
+The Agent Management Panel and Oz web app Runs page include two categories of agent activity.
 
 #### Interactive agents
 
-* Initiated from the Warp desktop app.
+* Initiated from the Warp app.
 * The conversation is owned by you. It opens locally in Warp, and can be shared via a link when needed.
 * Credit usage reflects inference.
 
@@ -51,9 +56,23 @@ In the **Personal** tab, you can view all of the interactive and cloud agent con
 
 ---
 
+### Inspect or review an agent run
+
+Use the Agent Management Panel or Oz web app Runs page as the starting point when a teammate asks, "What did the agent do?"
+
+1. In the agents list, use the filter menu to filter by source, day, creator, or status.
+2. Select the matching row to open the shared session or local conversation.
+3. Inspect the prompt, plan, commands, logs, outputs, and follow-up messages where available.
+4. Share the session link with teammates if they need to review the same context.
+5. For PR-producing workflows, include the session link alongside the PR link so reviewers can inspect both the code diff and the agent's execution context.
+
+For cloud agent runs, the session opens in [Cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/). For local interactive agents, the conversation opens in Warp and can be shared with [Agent Session Sharing](/agent-platform/local-agents/session-sharing/).
+
+---
+
 ### The agents list
 
-Each row represents a single item in the management view (either an interactive conversation or a cloud agent run). The list is intended to be scannable: you should be able to understand “what happened” without opening anything.
+Each row represents a single item in the agents list (either an interactive conversation or a cloud agent run). The list is intended to be scannable: you should be able to understand “what happened” without opening anything.
 
 #### Fields you’ll see
 
@@ -84,10 +103,10 @@ Warp uses a small set of statuses to help you quickly identify what needs attent
 
 **The primary interaction is simple:**
 
-* Clicking a cloud agent row opens the [shared session](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for that run (logs/messages/output).
+* Clicking a cloud agent row opens the [shared session](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for that run (prompt, plan, commands, logs, messages, and output where available).
 * Clicking an interactive row opens the conversation locally in the Warp app.
 
-This makes the management view a navigation surface: find the thing you care about, click once, and you’re in the right context to inspect or continue work.
+This makes the agents list a navigation surface: find the thing you care about, click once, and you’re in the right context to inspect or continue work.
 
 ### Filtering
 
@@ -106,8 +125,8 @@ This is the fastest way to isolate "everything that failed today," "runs from Sl
 
 When a parent agent spawns one or more child agents through [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/), the parent and each child are tracked as separate runs. Where you see them depends on the surface:
 
-* **Local children in the Warp app** - while you're viewing the parent agent, an orchestration pill bar above the agent view header shows one pill per child with a live status badge. Click a child pill to switch the pane to that child's conversation in place; click the parent pill - or the breadcrumb that replaces the pill bar while you're viewing a child - to return. Local children don't appear as separate rows in the management view list.
-* **Cloud children in the Warp app** - appear in the management view list as their own rows alongside the parent and other runs. Filter by source, status, or creator to isolate them.
+* **Local children in the Warp app** - while you're viewing the parent agent, an orchestration pill bar above the agent view header shows one pill per child with a live status badge. Click a child pill to switch the pane to that child's conversation in place; click the parent pill - or the breadcrumb that replaces the pill bar while you're viewing a child - to return. Local children don't appear as separate rows in the Agent Management Panel list.
+* **Cloud children in the Warp app** - appear in the Agent Management Panel list as their own rows alongside the parent and other runs. Filter by source, status, or creator to isolate them.
 * **Cloud children in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/)** - grouped under the parent's row on the Runs page, and surfaced together inside the parent's detail pane on a **Sub-agents** tab.
 
 The parent's own status reflects only its work - a parent can finish successfully while a child is still running or has failed. To verify that an orchestration completed, check each child individually from the pill bar (in the Warp app) or the **Sub-agents** tab (in the Oz web app).

src/content/docs/agent-platform/cloud-agents/mcp.mdx

@@ -118,6 +118,7 @@ As a workaround, you can pass Figma mockups as **image context** to the agent, w
 
 ## Learn more
 
+* [Connect developer tools to agents with MCP workflows](/guides/external-tools/using-mcp-servers-with-warp/) — choose between local, cloud, and shared MCP setup paths
 * [MCP Servers (CLI reference)](/reference/cli/mcp-servers/) — how to pass MCP configuration using the `--mcp` flag
 * [Model Context Protocol (MCP)](/agent-platform/capabilities/mcp/) — configuring MCP servers in Warp for local agents
 * [Environments](/agent-platform/cloud-agents/environments/) — set up the runtime context (repo, image, startup commands) for cloud agent tasks