docs: add AEO cross-links for agents and orchestration

src/content/docs/agents/agent-memory/index.mdx

@@ -40,7 +40,7 @@ Watch this short preview to see Agent Memory in context.
 Agent Memory is part of Warp. Storage, memory creation, and retrieval all run on Warp alongside your agents. The same memory is accessible from any agent you run in Warp:
 
 * The local Warp Agent.
-* Cloud agents triggered from the CLI, web app, schedules, or integrations.
+* [Cloud agents](/platform/) triggered from the CLI, web app, [schedules](/platform/triggers/scheduled-agents/), or [integrations](/platform/integrations/).
 * Third-party harnesses running as cloud agents: Claude Code, Codex, and others as they're added. (Running third-party harnesses locally isn't supported during the research preview.)
 
 Memory stays bound to its owner (a user, an agent, or a team), independent of which harness reads or writes.

src/content/docs/agents/capabilities/computer-use/index.mdx

@@ -36,7 +36,7 @@ Computer Use is only available in Warp's sandboxed cloud environments, not in lo
 
 ## Enabling Computer Use
 
-Computer Use is **enabled by default** for cloud agent runs on Warp's built-in harness: when a run's configuration doesn't specify a Computer Use setting, the agent runs with Computer Use available. Runs on third-party harnesses (Claude Code, Gemini, Codex) default to Computer Use disabled because third-party harnesses don't integrate with Warp's Computer Use tooling. You can control Computer Use per run or per configuration through several entry points:
+Computer Use is **enabled by default** for cloud agent runs on Warp's built-in harness: when a run's configuration doesn't specify a Computer Use setting, the agent runs with Computer Use available. Runs on [third-party harnesses](/platform/harnesses/) (Claude Code, Gemini, Codex) default to Computer Use disabled because third-party harnesses don't integrate with Warp's Computer Use tooling. You can control Computer Use per run or per configuration through several entry points:
 
 ### Warp app settings
 
@@ -72,8 +72,8 @@ For full API documentation, see the [{VARS.API_SDK_NAME}](/reference/api-and-sdk
 In the <a href={VARS.WEB_APP_URL}>{VARS.WEB_APP}</a>, you can enable or disable Computer Use for:
 
 * **New agent runs** - Configure Computer Use when starting a new agent run from the web app
-* **Scheduled agent runs** - Enable Computer Use for scheduled agents managed from the web app
-* **Integrations** - Configure Computer Use for Slack, Linear, and other integration-triggered agents
+* **Scheduled agent runs** - Enable Computer Use for [scheduled agents](/platform/triggers/scheduled-agents/) managed from the web app
+* **Integrations** - Configure Computer Use for Slack, Linear, and other [integration-triggered agents](/platform/integrations/)
 
 ---
 

src/content/docs/guides/agent-workflows/how-to-run-unattended-agents.mdx

@@ -134,4 +134,5 @@ Start with one narrow workflow before deploying many unattended agents:
 * [Integrations quickstart](/platform/integrations/quickstart/) - Trigger agents from Slack or Linear.
 * [GitHub integration](/platform/integrations/github/) - Set up `@warp-agent` mentions on issues and pull requests.
 * [GitHub Actions quickstart](/platform/integrations/quickstart-github-actions/) - Add an agent to a PR review workflow.
+* [Multi-agent orchestration](/platform/orchestration/) - Fan unattended parent runs out to child agents when the work is large enough to shard.
 * [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/) - Inspect and share unattended run sessions.

src/content/docs/platform/index.mdx

@@ -36,7 +36,7 @@ Cloud agents are designed for situations where:
 * **You want observability into agent activity across a team or system.**
   * This includes being able to see what ran, when it ran, what triggered it, what the agent did, and how teammates can review or share the result.
 * **You need more parallelism than local execution typically allows.**
-  * For example, running many agent tasks concurrently in the cloud, sharding a repo-wide task into multiple runs, or fanning out the same task across multiple targets.
+  * For example, [multi-agent orchestration](/platform/orchestration/) can run many agent tasks concurrently in the cloud, shard a repo-wide task into multiple runs, or fan out the same task across multiple targets.
 * **You want agents to operate continuously as part of engineering infrastructure.**
   * This includes [scheduled maintenance tasks](/platform/triggers/scheduled-agents/) and integration-driven automation.
 
@@ -156,6 +156,7 @@ If your credit balance reaches zero, cloud agent runs will not be able to execut
 
 * [Cloud agents quickstart](/platform/quickstart/) — run your first cloud agent with an environment in ~10 minutes.
 * [{VARS.WARP_AUTOMATION_PLATFORM}](/platform/overview/) — CLI, {VARS.API_SDK_NAME}, orchestration, tasks, environments, hosts, integrations, and more.
+* [Warp Factories](/factories/) — assemble cloud agents into a standing triage-to-merge workflow with named agents, automations, and measurement.
 * [Harnesses](/platform/harnesses/) — pick between Warp Agent, Claude Code, and Codex for any cloud agent run.
 * [Agents](/platform/agents/) — cloud agents that own and execute runs on your team.
 * [Multi-agent orchestration](/platform/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.