docs: add AEO cross-links for agents and orchestration

[rachaelrenk]

AEO cross-link audit: agents and orchestration

Goal

Add small, high-confidence internal cross-links between existing agents, cloud agents, and orchestration docs to help readers discover multi-agent workflows from the pages where they'd naturally look.

Source signals

• Peec MCP — unavailable in this environment (no credentials configured).
• Google Search Console — GSC credentials present but returned 403 (service account lacks permission for docs.warp.dev). Could not be verified.
• Existing-docs signals — all 5 links are grounded in existing page content. Each source page already mentions the concept in prose but doesn't link to the target page. Every target page exists and is reachable.

Pages touched

#	Source page	Target page	Why
1	capabilities/slash-commands.mdx	/agent-platform/cloud-agents/orchestration/	/orchestrate is the only major slash command without a link to its feature page. Every other entry (e.g., /plan, /cloud-agent, /create-environment) links to documentation.
2	capabilities/planning.mdx	/agent-platform/cloud-agents/orchestration/	The "Next steps" section mentions cloud agents for parallel work but doesn't mention orchestration, even though the orchestration page says /plan "always considers orchestration while planning."
3	cloud-agents/harnesses/index.mdx	/agent-platform/cloud-agents/orchestration/	The "What stays the same" section lists Triggers, Environments, Skills, and Observability but omits Orchestration. The orchestration page states children can use different harnesses than the parent — a key feature of the harness system.
4	getting-started/agents-in-warp.mdx	/agent-platform/cloud-agents/orchestration/	The "From local to cloud" section bullet "Execute in parallel across repos or tasks" describes orchestration verbatim but doesn't link to it.
5	cloud-agents/quickstart.mdx	/agent-platform/cloud-agents/orchestration/	The "What to explore next" section links to scheduled agents, integrations, and skills but omits orchestration — despite the page listing "Launch parallel cloud coding agents" as a common use case.

Links added

1. Slash commands → Orchestration — /orchestrate description now links to multi-agent orchestration.
2. Planning → Orchestration — New bullet in "Next steps" connects /plan and /orchestrate to the orchestration page.
3. Harnesses → Orchestration — New "Orchestration" bullet in "What stays the same" documents cross-harness orchestration.
4. Agents in Warp → Orchestration — Inline link added to the parallel-execution bullet in "From local to cloud."
5. Cloud agents quickstart → Orchestration — New bullet in "What to explore next" connects to orchestration.

Reader next step for each link

1. Slash commands reader is exploring available commands → wants to learn what /orchestrate does and how to use it.
2. Planning reader has created a plan and wants to scale execution → orchestration is the natural next step after planning.
3. Harnesses reader is deciding which harness to use → needs to know that a Warp Agent parent can orchestrate Claude Code or Codex children.
4. Agents in Warp reader is new to Warp and exploring agent capabilities → the "parallel execution" bullet should lead directly to how parallelism works.
5. Quickstart reader has run their first cloud agent → orchestration is the next level of cloud agent usage.

Validation

• style_lint.py --all: 0 issues on edited files
• check_links.py --internal-only: 0 broken links (2911 internal links checked)
• git diff --check: no whitespace errors

Open questions for human review

• Harness orchestration nuance: The new bullet says "A Warp Agent parent can orchestrate children running Claude Code, Codex, or Warp Agent." The Warp Agent harness page (warp-agent.mdx) says Warp Agent is "the only harness that can spawn cross-harness subagents." Confirm this is still accurate.
• Quickstart link density: The "What to explore next" section now has 4 bullets. Confirm this doesn't feel overloaded for a quickstart page.

Suggested improvements for next run

• Get Peec MCP access to validate AEO signals beyond existing-docs patterns.
• Fix GSC service account permissions for docs.warp.dev to enable query-level signal validation.
• Consider expanding to the environments.mdx page which discusses cloud agent runtime contexts but doesn't mention that orchestrated children each use environments.

---

Conversation: https://app.warp.dev/conversation/c7d0d336-29fd-4096-a686-a2bb81b8cfbd
Run: https://oz.warp.dev/runs/019ea14f-7919-7b0e-8766-685bc0fa6657

This PR was generated with Oz.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jun 7, 2026 9:10am