diff --git a/src/content/docs/agent-platform/agent-memory/index.mdx b/src/content/docs/agent-platform/agent-memory/index.mdx index c0f3ca19..afd92cf2 100644 --- a/src/content/docs/agent-platform/agent-memory/index.mdx +++ b/src/content/docs/agent-platform/agent-memory/index.mdx @@ -6,6 +6,8 @@ description: >- sidebar: label: "Agent Memory (Research Preview)" --- +import VideoEmbed from '@components/VideoEmbed.astro'; + :::caution Agent Memory is in **research preview** and is enabled per team for design partners. [Join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access for your team. ::: @@ -14,6 +16,10 @@ Agent Memory is a persistent memory system that lives on Oz and is shared across Memory creation and retrieval are asynchronous and run in the background, so they don't consume tokens or add latency to the active task. +Watch this short preview to see Agent Memory in context. + + + [Join the Agent Memory waitlist](https://warp.dev/oz/agent-memory#waitlist). ## Key features diff --git a/src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx b/src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx index 6b6c98ac..faadaf15 100644 --- a/src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx +++ b/src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx @@ -6,9 +6,14 @@ description: >- sidebar: label: "Cloud to cloud" --- +import VideoEmbed from '@components/VideoEmbed.astro'; Cloud-to-cloud handoff in Warp lets you send follow-up instructions to a finished cloud agent run and continue it in a fresh cloud session. The run keeps the same conversation and restores the prior workspace state, so the agent can pick up where it left off instead of starting over. +Watch this walkthrough to see how cloud-to-cloud handoff continues a cloud agent run without losing the prior session context. + + + Use this handoff direction when: * You want to send a follow-up to a cloud agent after its session has ended. diff --git a/src/content/docs/agent-platform/cloud-agents/handoff/local-to-cloud.mdx b/src/content/docs/agent-platform/cloud-agents/handoff/local-to-cloud.mdx index d1dd79a8..5ef5ee51 100644 --- a/src/content/docs/agent-platform/cloud-agents/handoff/local-to-cloud.mdx +++ b/src/content/docs/agent-platform/cloud-agents/handoff/local-to-cloud.mdx @@ -6,9 +6,14 @@ description: >- sidebar: label: "Local to cloud" --- +import VideoEmbed from '@components/VideoEmbed.astro'; Local-to-cloud handoff in Warp promotes an active local Warp Agent conversation into a cloud agent run. Warp forks the conversation, snapshots your uncommitted workspace changes, and sends both to the cloud so the agent can continue the same task with the context and files it needs. +Watch this walkthrough to see how to move a local Warp Agent conversation into a cloud agent run. + + + Use this handoff direction when: * You have a long-running task and don't want to keep your laptop awake. diff --git a/src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx b/src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx index ffa21d98..fb731a5b 100644 --- a/src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx +++ b/src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx @@ -7,9 +7,14 @@ description: >- sidebar: label: "Overview" --- +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. + + + ## What stays the same Third-party harnesses inherit the same Oz platform features as Warp Agent: diff --git a/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx b/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx index ba07e46b..3408e749 100644 --- a/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx +++ b/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx @@ -4,9 +4,14 @@ description: Coordinate parent and child agents across local and cloud runs to b sidebar: label: "Orchestration" --- +import VideoEmbed from '@components/VideoEmbed.astro'; Multi-agent orchestration lets one agent spawn and coordinate other agents to parallelize work, delegate specialized tasks, or verify another agent's output. The parent/child model works from the Warp app, the [Oz CLI](/reference/cli/), and the [Oz API](/reference/api-and-sdk/), and supports local, cloud, and mixed execution. +Watch this walkthrough to see how a cloud agent can coordinate a team of agents in the cloud. + + + This page covers the orchestration model and the patterns it supports. To learn how to start an orchestrated run, see [Running orchestrated agents](/agent-platform/cloud-agents/orchestration/multi-agent-runs/). ## The parent/child model diff --git a/src/content/docs/agent-platform/cloud-agents/orchestration/multi-agent-runs.mdx b/src/content/docs/agent-platform/cloud-agents/orchestration/multi-agent-runs.mdx index 8a3ec0ee..96bc35c7 100644 --- a/src/content/docs/agent-platform/cloud-agents/orchestration/multi-agent-runs.mdx +++ b/src/content/docs/agent-platform/cloud-agents/orchestration/multi-agent-runs.mdx @@ -4,9 +4,14 @@ description: Start multi-agent orchestrations from the Warp app, the Oz CLI, the sidebar: label: "Running orchestrated agents" --- +import VideoEmbed from '@components/VideoEmbed.astro'; An orchestrated run starts with a parent agent that spawns one or more child agents. You can start a parent from the Warp app, the Oz CLI, the Oz web app, or the Oz API. Use orchestrated runs to review a plan before fan-out, execute children locally or in the cloud, and inspect parent and child conversations as they work. +Watch this walkthrough to see how to start and inspect an orchestrated agent run from Warp. + + + ## Before you start Pick where the parent will run. Every orchestration starts with a single parent that spawns children: