docs: add AEO cross-links for agents and orchestration

[rachaelrenk]

AEO cross-link audit: agents and orchestration

Small, high-confidence internal cross-link additions for the agents, cloud agents, and orchestration topic area. Scope is limited to cross-linking existing pages — no new pages, no rewrites.

Goal

Identify small internal cross-link improvements for agents, cloud agents, and orchestration docs that help readers continue a real workflow.

Source signals

From the Peec snapshot at buzz/aeo-snapshots/docs/agents-orchestration/latest.json (window 2026-05-05 to 2026-06-04), high-volume docs-adjacent prompts include:

• "how do I set up AI coding agents to run on a schedule or in the background?" (high)
• "what's the best platform for scheduling and managing AI coding agents across a team?" (high)
• "how do development teams track and observe what their AI coding agents are doing in real time?" (high)
• "how do I trigger AI coding agents automatically from Slack, Linear, or GitHub?" (high)
• "what are the best tools for managing multiple AI coding agents?"

The snapshot's open questions also ask which page should be the canonical target for monitoring and reviewing cloud agent runs. Managing cloud agents (the Agent Management Panel + Oz web app Runs page) is that canonical target, and multiple pages were missing a link to it.

Google Search Console credentials were available in the environment, but no GSC query was run for this audit — the Peec prompts plus the repo-grounded gap on the hub pages were sufficient. No secret value was read, logged, or committed.

Pages touched

• src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx — the CLI reference for Scheduled Agents did not link to the guided, no-CLI quickstart, despite scheduling being the strongest Peec signal cluster.
• src/content/docs/agent-platform/cloud-agents/triggers/index.mdx — Thin hub page that listed trigger types but never pointed readers to where triggered runs are monitored.
• src/content/docs/agent-platform/cloud-agents/integrations/index.mdx — Integrations hub that explained setup but never linked to the run-monitoring surface for integration-triggered runs.
• src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx — An under-linked legacy guide (1 existing link) that mentions agent notifications and a run-review surface without linking either.

Links added

1. triggers/scheduled-agents.mdx to triggers/scheduled-agents-quickstart.mdx — gives readers on the CLI reference a path to the guided web-app setup. The reverse link (quickstart to reference) already exists, confirming the relationship.
2. triggers/index.mdx to managing-cloud-agents — Added a sentence after the trigger types list: after a trigger fires, track and review the resulting runs from the Agent Management Panel and Oz web app Runs page. Backed by the "track and observe in real time" and "scheduling and managing across a team" prompts.
3. integrations/index.mdx to managing-cloud-agents — Added a "Managing cloud agents" item to the existing "Get started" list to monitor and review integration-triggered runs. Backed by the "track and observe in real time" and "trigger from Slack, Linear, or GitHub" prompts.
4. guides/.../running-multiple-agents-at-once-with-warp.mdx to capabilities/agent-notifications.mdx — the page lists "Notifications when blocked or completed" but never linked the notifications setup doc.
5. guides/.../running-multiple-agents-at-once-with-warp.mdx to cloud-agents/managing-cloud-agents.mdx — the "Reviewing all active agents" section describes monitoring active/completed runs; the Agent Management Panel is the canonical observability surface (matches the Peec "observe in real time" / "managing multiple" signals).

Reader next step

• A reader on the Scheduled Agents CLI reference who wants the fastest setup can jump straight to the quickstart.
• A reader who just set up a trigger or integration next wants to know where the resulting runs appear and how to review them across the team. Both hub pages previously dead-ended without pointing to the canonical monitoring surface; these links complete that workflow.
• A reader running multiple agents who wants notifications can reach setup instructions; one who wants to track all runs across their account/team can reach the Agent Management Panel.

Open questions for human review

• Confirm Managing cloud agents is the preferred canonical monitoring target over the standalone Oz web app page for these hub-page links (the snapshot raises this as an open question). Managing cloud agents was chosen because it documents both the Agent Management Panel and the Oz web app Runs page in one place.
• The "Run multiple agents at once" guide uses legacy terminology ("Agent Mode Dashboard", "Task List panel"). This PR only adds cross-links and does not rename these; a follow-up could align them with current terminology (Agent Management Panel, Task lists).
• GSC was available but not queried. A future run with a defined property/query path could confirm or expand these links with live search-query data.

Follow-up recommendations (out of scope for this cross-link pilot)

• The Slack and Linear integration pages link "Environment Setup" to the integrations index rather than the dedicated environments page. That is an accuracy/link-target fix rather than a cross-link addition, so it was left out of this audit.
• Consider a reverse cross-link from scheduled-agents.mdx / integrations pages to orchestration/ for the "managing multiple agents" cluster, if it reads as a natural next step rather than link stuffing.

---

Conversation: https://app.warp.dev/conversation/59a539f1-3676-4526-aade-d7038c0f4ae1
Run: https://oz.warp.dev/runs/019eca82-5919-7e6d-9c89-b586eea9db27

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 16, 2026 8:44pm

[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 three targeted internal cross-links between existing Agent Platform and guide pages for scheduled agents, notifications, and agent management. The linked destinations exist and the added context is consistent with the source pages and the PR's AEO cross-linking scope.

Concerns

No blocking concerns found. No security findings were identified, and no approved or repository spec context was available for implementation drift review.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

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

Powered by Oz

[rachaelrenk]

/oz-review

[oz-for-oss]

@rachaelrenk

I'm re-reviewing this pull request in response to a review 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 focused internal cross-links from cloud-agent trigger and integration pages, plus an existing multi-agent guide, to the scheduled agents quickstart, managing cloud agents, and agent notifications pages. The linked targets exist in the docs tree, the additions stay within the stated cross-linking scope, and the docs-only diff did not introduce security concerns.

Concerns

• None.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

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

Powered by Oz