docs: add AEO cross-links for agents and orchestration - #612
Conversation
Link Remote Control from Codex and OpenCode, connect Factories and harnesses docs to multi-agent orchestration, and point factory automations at scheduled agents.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR was generated with Warp. Comment |
|
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 |
![warp-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 AEO-focused internal cross-links from Codex, OpenCode, Factories, and harness docs to Remote Control, orchestration, and scheduling pages. Most links are relevant and resolve to existing docs, but one factory automation link points readers to the standalone Scheduled Agents setup model rather than factory automation scheduling.
Concerns
- The factory automation schedule link should point to factory-specific automation or scheduling guidance, not the standalone Scheduled Agents reference.
- Security pass: no findings; this is a documentation-only link change with no code, config, secrets, or dependency changes.
- Spec context: no approved or repository spec context was provided, so there is no implementation/spec drift to assess.
Verdict
Found: 0 critical, 1 important, 0 suggestions
Request changes
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Remove duplicated Remote Control links from the Related pages lists on codex.mdx and opencode.mdx (already linked in Supported Warp features, per rachaelrenk's review comments). Repoint the factory automations schedule link at the factory-as-code schedule trigger reference instead of the standalone Scheduled Agents guide, per the automated review's important finding. Co-Authored-By: Warp <agent@warp.dev>
1 participant
AEO brief
Goal
Identify small internal cross-link improvements for agents, cloud agents, and orchestration docs.
Source signals
/agents/cli-agents/remote-control/,/agent-platform/cli-agents/remote-control/), multi-agent guide traffic (/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/), platform/orchestration impressions, factory queries (warp factory→/factories/), and schedule/cloud-agent language.Pages touched
src/content/docs/agents/cli-agents/codex.mdx— align Remote Control with Claude Code pattern.src/content/docs/agents/cli-agents/opencode.mdx— same for OpenCode.src/content/docs/factories/index.mdx— link Automation Platform row to multi-agent orchestration.src/content/docs/factories/factory-agents.mdx— link factory automations to the schedule trigger reference.src/content/docs/platform/harnesses/index.mdx— link orchestration in billing copy and Related pages.Links added
/agents/cli-agents/remote-control//agents/cli-agents/remote-control//platform/orchestration//factories/factory-as-code/#triggersschedulescheduletrigger reference, not the standalone Scheduled Agents guide./platform/orchestration/Reader next step
Review feedback addressed
schedulelink as pointing at the standalone Scheduled Agents setup model instead of factory automation scheduling. Repointed it at/factories/factory-as-code/#triggersschedule, the automation schema's schedule trigger reference.Open questions for human review
/orchestrate. Flag if product prefers only/factories/how-factories-work/here.Test plan
style_lint/ broken internal link check on changed tree#triggersscheduleanchor)npm run build(Astro build) succeedsOz run: https://app.warp.dev/conversation/f6a9c10f-5b3d-4cd3-93dd-28c9b81ccc0c