docs: add AEO cross-links for agents and orchestration

[warp-factories]

AEO brief

Goal: Identify small internal cross-link improvements for agents, cloud agents, and orchestration docs.

Recommendation: Update existing pages with high-confidence internal cross-links only (no new pages, no rewrites).

Source signals:

• Peec (available): Cloud Agent Orchestration and Coding Agents prompts over the last 30 days include high-volume journeys such as running coding agents overnight in the cloud, steering/taking over cloud sessions, sharing live sessions, scheduling/managing agents across a team, multi-agent orchestration vs management, triggering agents from Slack/Linear/GitHub, and running multiple agents in parallel from a terminal.
• GSC (available via sc-domain:warp.dev): Strong docs traffic on Remote Control, environments, orchestration, handoff, managing cloud agents, and viewing cloud agent runs; queries include warp agent orchestration, warp cloud agents, cloud agents, and warp software factory.
• Existing docs: Several high-traffic pages already mention related concepts (parallel agents, overnight/unattended work, environments as runtime for triggers) but did not always link the next-step docs.

Vocabulary map:

• Users/answer engines say: run AI coding agents overnight without keeping my computer on
  Docs should say: hand off a local conversation to a cloud agent run, or start a scheduled/unattended cloud agent
• Users/answer engines say: share a live AI agent session / take over and steer
  Docs should say: Remote Control for CLI agent sessions; cloud agent session sharing for cloud runs
• Users/answer engines say: multi-agent orchestration / run multiple agents in parallel
  Docs should say: multi-agent orchestration and the parallel agents guide

Content scope:

• Include - Internal cross-links from environments, Remote Control, Agents in Warp, viewing cloud agent runs, and local-to-cloud handoff into orchestration, handoff, schedules/integrations, and related guides.
• Avoid - New pages, keyword stuffing, related-link dumps on already dense hub pages, broad SEO rewrites.

Pages touched / links added:

Source	Target	Reader next step
platform/environments.mdx	Integrations overview, Scheduled Agents, Multi-agent orchestration, Managing cloud agents	After defining an environment, wire it to a trigger, schedule, or orchestrated fan-out and inspect runs.
agents/cli-agents/remote-control.mdx	Handoff overview, How to run multiple AI coding agents	Move from monitoring a laptop CLI session to unattended cloud work or parallel local fleets.
agents/getting-started/agents-in-warp.mdx	Multi-agent orchestration, Handoff	Scale from simultaneous local agents to orchestrated fan-out or cloud handoff.
platform/viewing-cloud-agent-runs.mdx	Multi-agent orchestration, Remote Control	From inspecting one cloud session, find parent/child fleets or publish a local CLI session.
platform/handoff/local-to-cloud.mdx	Multi-agent orchestration, Viewing cloud agent runs	After handoff, fan out parallel children and open the cloud session to steer.

Open questions for human review:

• None blocking. Related-pages sections were preferred over mid-paragraph stuffing to keep density low.

Test plan

• style_lint.py --changed
• check_links.py --internal-only
• git diff --check
• Confirmed link targets exist on latest origin/main

Oz run: https://app.warp.dev/conversation/79e45390-6945-43b4-aa11-70e9ecd3061c

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 17, 2026 6:26pm

[oz-for-oss]

@rachaelrenk

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR adds targeted internal cross-links across agents, handoff, environments, Remote Control, and cloud-agent viewing docs to connect related workflows for AEO-driven discovery. The added links point to existing pages and there are no blocking security or spec-drift concerns.

Concerns

• One related-page description could be tightened to avoid implying orchestration itself spawns the parent or that all cloud runs share one environment.

Verdict

Found: 0 critical, 0 important, 1 suggestions

Approve with nits

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[rachaelrenk]

LGTM!