docs: add AEO cross-links for agents and orchestration#183
Conversation
Add 4 internal cross-links connecting agent platform pages to the orchestration docs: - planning.mdx: link to orchestration from Next Steps (the /plan command proposes orchestration when the task benefits) - agents-in-warp.mdx: link to orchestration in the From local to cloud section where parallel execution is mentioned - harnesses/index.mdx: add Orchestration to the What stays the same list (parent and child can run different harnesses) - environments.mdx: note that orchestrated child agents each get their own environment in the execution flow Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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 Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds targeted internal cross-links from planning, agents overview, harnesses, and environments pages to the multi-agent orchestration docs. The links are directionally useful for AEO and reader navigation, but one added sentence overstates how orchestrated child environments work and conflicts with the orchestration page's cloud-local execution model.
Concerns
- The environments page now says each child agent gets its own environment, but orchestrations can also run children inside the parent's cloud environment when shared state is needed.
- The planning cross-link would be more accurate if it made the user approval step explicit before child agents launch.
- No security findings. No approved spec context was provided for implementation drift review.
Verdict
Found: 0 critical, 1 important, 1 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| 3. **Environment** – The task uses an environment to define execution context | ||
| 4. **Host** – The environment runs on a host (Warp-hosted or self-hosted infrastructure). | ||
| 5. **Agent execution** – The workflow runs in the prepared environment | ||
| 5. **Agent execution** – The workflow runs in the prepared environment. In [orchestrated runs](/agent-platform/cloud-agents/orchestration/), each child agent gets its own environment so that parallel agents are isolated from each other. |
There was a problem hiding this comment.
Cloud → cloud-local mode, where children run inside the parent's cloud environment instead of getting separate environments.
| 5. **Agent execution** – The workflow runs in the prepared environment. In [orchestrated runs](/agent-platform/cloud-agents/orchestration/), each child agent gets its own environment so that parallel agents are isolated from each other. | |
| 5. **Agent execution** – The workflow runs in the prepared environment. In [orchestrated cloud runs](/agent-platform/cloud-agents/orchestration/), child agents can run in separate environments for isolation or inside the parent's cloud environment when they need shared state. |
|
|
||
| * **[Interactive Code Review](/agent-platform/local-agents/interactive-code-review/)** - Leave inline comments on agent-generated diffs and have the agent revise in one pass. | ||
| * **[Cloud Agents quickstart](/agent-platform/cloud-agents/quickstart/)** - Run agents in the cloud for longer tasks, background automation, or parallel work across repos. | ||
| * **[Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/)** - When `/plan` detects that a task benefits from parallel work, it proposes an orchestration config that spawns child agents to divide the work. |
There was a problem hiding this comment.
💡 [SUGGESTION] Clarify that /plan proposes orchestration for approval before child agents launch.
| * **[Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/)** - When `/plan` detects that a task benefits from parallel work, it proposes an orchestration config that spawns child agents to divide the work. | |
| * **[Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/)** - When a `/plan` task benefits from parallel work, the agent can propose an orchestration config for you to approve before child agents divide the work. |
|
First test run; made some tweaks to skill used by scheduled agent so closing this PR in favor of next week's run |
1 participant
AEO cross-link audit: agents, cloud agents, and orchestration
Goal
Identify small internal cross-link improvements for agents, cloud agents, and orchestration docs — the pilot topic area for the AEO cross-link audit skill.
Source signals
Google Search Console (March–June 2026):
agent-platform/rootThese queries indicate users searching for orchestration and multi-agent concepts are landing on pages that don't link to the orchestration docs.
Existing-docs signals:
planning.mdxdocuments/plan, which is one of the two entry points for orchestration, but didn't link to orchestrationagents-in-warp.mdxmentions "Execute in parallel across repos or tasks" without explaining howharnesses/index.mdxlists shared platform features but omitted orchestration, even though orchestration supports mixed harnessesenvironments.mdxdescribes the execution flow without mentioning how orchestration uses environmentsPeec: Not available in this environment. Recommendations are grounded in GSC + repo signals only.
Pages touched
capabilities/planning.mdx/planproposes orchestration when beneficial — readers learning about planning should discover thisgetting-started/agents-in-warp.mdxcloud-agents/harnesses/index.mdxcloud-agents/environments.mdxLinks added
planning.mdx→ Next steps/agent-platform/cloud-agents/orchestration//planwants to know they can use it to coordinate multiple agentsagents-in-warp.mdx→ From local to cloud/agent-platform/cloud-agents/orchestration/harnesses/index.mdx→ What stays the same/agent-platform/cloud-agents/orchestration/#where-parent-and-child-agents-can-runenvironments.mdx→ Execution flow/agent-platform/cloud-agents/orchestration/Open questions for human review
#where-parent-and-child-agents-can-runanchor — verify this renders correctly in the live Astro build.Conversation: https://app.warp.dev/conversation/3b0029f0-d95d-4f95-8fc6-8b13c681ed8f
Run: https://oz.warp.dev/runs/019e9702-c000-77a0-b913-10c63bc02ce1
This PR was generated with Oz.