docs: add AEO cross-links for agents and orchestration

[warp-factories]

Summary

Adds high-confidence internal cross-links for agents, cloud agents, and orchestration docs based on Peec and Google Search Console signals from the last ~30 days.

AEO brief

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

Recommendation: Update existing pages only (no new pages). Ship a focused cross-link PR.

Source signals:

• Peec — Cloud Agent Orchestration topic: repeated query clusters for scheduling/managing AI coding agents across a team, overnight cloud runs, real-time observability/session sharing/takeover, Slack/Linear/GitHub triggers, and on-prem/self-hosted execution where source code stays on own servers.
• Peec — Coding Agents topic: strong demand for running Claude Code and Codex together, parallel multi-agent terminal workflows, and tools for managing multiple agents.
• Peec owned HOW_TO / ARTICLE actions: opportunity around agentic development workflows, software factory concepts, and agent rules/skills/docs configuration (used only as directional signal; this PR stays within cross-links).
• GSC (sc-domain:warp.dev, ~2026-07-31 to 2026-08-28): high impressions on codex cli, cloud agents, software factory, best terminal for claude code, agent cli, agentic development environment, plus strong docs traffic on CLI agent and cloud agent pages.
• Existing-docs signal: Claude Code / Codex cloud harness pages already describe schedules, Slack, and orchestration in prose without destination links; self-hosting already documents routing from schedules/integrations and monitoring without links to those product pages; handoff and multi-agent-run pages mention parallel variants, Slack/scheduled parents, and self-hosted children without links.

Vocabulary map:

• Users/answer engines say: “run AI coding agents overnight / on a schedule,” “track agents in real time,” “share live agent session / take over,” “code never leaves our servers,” “run Claude Code and Codex together / multiple agents in parallel,” “trigger agents from Slack/Linear/GitHub.”
• Docs should say: scheduled agents, Agent Management Panel / Runs page, Agent Session Sharing and Remote Control, self-hosting, multi-agent orchestration with Warp Agent parent + Claude Code/Codex children, integrations (Slack, Linear, GitHub Actions).

Content scope:

• Include — natural destination links where the source page already implies the next step.
• Avoid — new pages, keyword stuffing, dense link clusters, related-link lists that are not already present, broad SEO rewrites.

Pages touched

File	Why
platform/harnesses/claude-code.mdx	Cloud harness prose already lists schedules/Slack/orchestration; readers need the destination pages.
platform/harnesses/codex.mdx	Same as Claude Code; GSC/Peec heavily surface Codex + multi-agent journeys.
platform/self-hosting/index.mdx	Peec on-prem/self-host cluster; page already covers schedules, integrations, and monitoring.
platform/handoff/index.mdx	Bridges overnight/parallel cloud work and Slack/scheduled follow-ups into orchestration + triggers.
platform/orchestration/multi-agent-runs.mdx	Launch page for orchestration; needed links to triggers, self-hosting, and handoff.

Links added

Source	Target	Rationale / reader next step
Claude Code harness key features	Scheduled agents; Slack integration; Multi-agent orchestration	Reader launching Claude Code from a trigger wants the schedule/Slack setup, or parent/child orchestration model.
Claude Code related pages	Multi-agent orchestration; Managing cloud agents	After picking Claude Code as a child harness, inspect parent/child runs.
Codex harness key features	Scheduled agents; Slack integration; Multi-agent orchestration	Same journey for Codex cloud harness.
Codex related pages	Multi-agent orchestration; Managing cloud agents	Same as Claude Code.
Self-hosting managed model	Slack integration; Scheduled agents	Reader routing managed workers needs the trigger docs that set --host.
Self-hosting monitoring	Managing cloud agents; Agent Session Sharing	Reader asking how to observe self-hosted runs in real time.
Self-hosting related pages	Scheduled agents; Integrations; Managing cloud agents	Next steps after deploying a worker.
Handoff when-to-use	Multi-agent orchestration; Slack; Scheduled agents	Local→cloud for parallel variants; cloud→cloud after Slack/scheduled completion.
Handoff related pages	Multi-agent orchestration	Fan out after promoting a local session.
Running orchestrated agents (before you start)	Integrations; Slack; Scheduled agents; Self-hosting	Cloud parent triggers and private execution path.
Running orchestrated agents related pages	Scheduled agents; Self-hosting; Handoff	Recurring fan-out, private workers, and continuing finished parents.

Open questions for human review:

• Are “Linear issues” on the harness pages better left unlinked (as today) or should they also point at /platform/integrations/linear/ for parity with Slack?
• Self-hosting related-pages list grew by three items; prefer keeping them only as inline body links if the related list feels long?

Test plan

• python3 .agents/skills/check_for_broken_links/check_links.py --internal-only — 0 broken internal links
• git diff --check
• Confirmed each link target file exists on current tree and is not a vercel.json redirect source
• Human skim for voice and link density on the five pages

Plans:

• None

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 31, 2026 3:14pm

[warp-factories]

This PR was generated with Warp.

Comment @warp-agent on this PR to send it follow-up work.

  View origin