rachaelrenk · Sep 8, 2026 · Sep 7, 2026 · Sep 8, 2026 · Sep 8, 2026 · Sep 8, 2026
diff --git a/src/content/docs/agents/agent-memory/index.mdx b/src/content/docs/agents/agent-memory/index.mdx
@@ -13,7 +13,7 @@ import VideoEmbed from '@components/VideoEmbed.astro';
 Agent Memory is in **research preview** and is enabled per team for design partners. [Join the waitlist](https://www.warp.dev/oz/agent-memory#waitlist) to request access for your team.
 :::
 
-Agent Memory is a persistent memory system that lives on Warp and is shared across every supported agent harness, including the built-in Warp Agent, Claude Code, Codex, and others as they're added. Agents read from and write to this memory system as they run, so durable facts, decisions, and outcomes from one conversation are available to the next — regardless of which harness, machine, or teammate triggers the work.
+Agent Memory is a persistent memory system that lives on Warp and is shared across every supported [agent harness](/platform/harnesses/), including the built-in Warp Agent, Claude Code, Codex, and others as they're added. Agents read from and write to this memory system as they run, so durable facts, decisions, and outcomes from one conversation are available to the next — regardless of which harness, machine, or teammate triggers the work.
 
 Memory creation and retrieval are asynchronous and run in the background, so they don't consume tokens or add latency to the active task.
 
@@ -94,6 +94,7 @@ Agent Memory is rolling out to design partner teams during research preview. [Jo
 
 ## Related pages
 
+* [Harnesses in the {VARS.WARP_AUTOMATION_PLATFORM}](/platform/harnesses/) - Run Warp Agent, Claude Code, or Codex as cloud agents with shared platform features.
 * [Codebase Context](/agents/capabilities/codebase-context/) - Let agents understand your codebase through semantic indexing.
 * [Rules](/agents/capabilities/rules/) - Define global and project-level guidelines that shape agent behavior.
 * [Skills](/agents/capabilities/skills/) - Reusable, scoped instructions that teach agents how to perform specific tasks.

diff --git a/src/content/docs/agents/capabilities/codebase-context.mdx b/src/content/docs/agents/capabilities/codebase-context.mdx
@@ -116,7 +116,7 @@ Files excluded by ignore rules **do not** count toward your codebase's file limi
 
 ## Codebase Context in cloud agent runs
 
-Codebase Context is available in all cloud agent runs — including runs triggered from the CLI, API/SDK, integrations (Slack, Linear, GitHub Actions), and schedules — as long as Codebase Context is enabled for your account.
+Codebase Context is available in all [cloud agent runs](/platform/viewing-cloud-agent-runs/) — including runs triggered from the CLI, API/SDK, integrations (Slack, Linear, GitHub Actions), and schedules — as long as Codebase Context is enabled for your account.
 
 **No additional configuration is needed.** If Codebase Context is enabled, cloud agents use it automatically.
 

diff --git a/src/content/docs/agents/cli/reference.mdx b/src/content/docs/agents/cli/reference.mdx
@@ -133,7 +133,7 @@ Type `/` at the start of the input to open the slash command menu. Commands that
 | `/export-to-clipboard` | | Export the current conversation to the clipboard as Markdown |
 | `/export-to-file` | `[filename]` | Export the current conversation to a Markdown file |
 | `/fork` | `[prompt]` | Fork the current conversation into a copy, optionally sending a prompt in the copy |
-| `/handoff` | `[prompt]` | Hand off this conversation to a cloud agent |
+| `/handoff` | `[prompt]` | Hand off this conversation to a cloud agent. See [cloud handoff and orchestration](/agents/cli/cloud-and-orchestration/#hand-off-to-a-cloud-agent) |
 | `/logout` | | Log out of Warp |
 | `/manage-billing` | | Open your team's billing page in the browser |
 | `/mcp` | | View and manage MCP servers |

diff --git a/src/content/docs/factories/factory-dashboard.mdx b/src/content/docs/factories/factory-dashboard.mdx
@@ -60,7 +60,7 @@ Click a work item to open its detail pane, which includes the prompt that starte
 
 A run is a single agent execution. A work item on **Activity** tracks one piece of work through the factory's stages and can span several runs as different agents pick it up. The team-level **Runs** page lists every run you have access to; a factory's **Runs** page lists only runs from that factory's agents.
 
-Click **New** on a factory's **Runs** page to send a prompt to the factory's foreman agent. Open a run to see its timeline and cost, plus a **Sub-agents** tab for an orchestrator run's child runs. From there you can view the agent's full session, stop or score the run, or turn it into a benchmark task.
+Click **New** on a factory's **Runs** page to send a prompt to the factory's foreman agent. Open a run to see its timeline and cost, plus a **Sub-agents** tab for child runs when the agent used [multi-agent orchestration](/platform/orchestration/). From there you can view the agent's full session, stop or score the run, or turn it into a benchmark task.
 
 {/* VISUAL: The Runs page with the New button, showing an empty or sample run list. */}
 

diff --git a/src/content/docs/platform/harnesses/warp-agent.mdx b/src/content/docs/platform/harnesses/warp-agent.mdx
@@ -18,7 +18,7 @@ Warp Agent is the same agent runtime that powers Agent Mode in the Warp terminal
 * **Full terminal and tool access** - Runs commands, edits files, reads logs, executes tests, navigates repos, and calls MCP servers, giving cloud runs the same toolbelt Warp Agent uses locally.
 * **Platform-native context** - Reads [Codebase Context](/agents/capabilities/codebase-context/), applies [Rules](/agents/capabilities/rules/), reuses saved [Skills](/agents/capabilities/skills/), and respects Memory and Warp Drive context with no extra setup.
 * **Multi-repo execution** - Clones every repo configured on the [environment](/platform/environments/) and works across them in a single run.
-* **Cross-harness orchestration parent** - A Warp Agent parent run can spawn Claude Code or Codex [subagents](/platform/) and coordinate their outputs. Other harnesses cannot act as parents in a multi-harness orchestration.
+* **Cross-harness orchestration parent** - A Warp Agent parent run can spawn Claude Code or Codex children and coordinate their outputs in [multi-agent orchestration](/platform/orchestration/). Other harnesses cannot act as parents in a multi-harness orchestration.
 * **No extra credentials** - Warp Agent uses your existing Warp account and credits. There's no separate API key to configure.
 
 ## How it works
@@ -33,13 +33,13 @@ Warp Agent supports the full Warp model catalog. Configure the model per [Agent
 
 ### Cross-harness orchestration
 
-Warp Agent is the orchestration host for multi-harness runs. A typical pattern looks like:
+Warp Agent is the orchestration host for multi-harness runs. [Multi-agent orchestration](/platform/orchestration/) covers the parent/child model, run states, and patterns; a typical multi-harness pattern looks like:
 
 1. A Warp Agent parent run analyzes a task and breaks it into subtasks.
-2. The parent dispatches Claude Code subagents for steps that need careful review and Codex subagents for high-volume edits.
+2. The parent dispatches Claude Code children for steps that need careful review and Codex children for high-volume edits.
 3. The parent collects results, resolves conflicts, and returns a single final output (a PR, a report, a Slack reply).
 
-Subagents run in the same environment as the parent and share the same secrets, MCP servers, and integrations. The transcript shows the full tree, so reviewers can see exactly which subagent did what.
+Children run in the same environment as the parent and share the same secrets, MCP servers, and integrations. The transcript shows the full tree, so reviewers can see exactly which child did what.
 
 ## When to choose Warp Agent
 
@@ -65,6 +65,7 @@ For a complete walkthrough, see the [Cloud agents quickstart](/platform/quicksta
 * [Harnesses in the {VARS.WARP_AUTOMATION_PLATFORM}](/platform/harnesses/) — choose between Warp Agent, Claude Code, and Codex.
 * [Claude Code with the {VARS.WARP_AUTOMATION_PLATFORM}](/platform/harnesses/claude-code/) — Claude Code as a cloud harness.
 * [Codex with the {VARS.WARP_AUTOMATION_PLATFORM}](/platform/harnesses/codex/) — Codex as a cloud harness.
+* [Multi-agent orchestration](/platform/orchestration/) — parent/child runs, including cross-harness children Warp Agent can spawn.
 * [Model choice](/agents/inference/model-choice/) — the model catalog Warp Agent routes across.
 * [Agent Profiles and permissions](/agents/capabilities/agent-profiles-permissions/) — configure the default model, autonomy, and tool access for Warp Agent.
 * [Skills as agents](/platform/skills-as-agents/) — turn a saved skill into a reusable Warp Agent run.