From d1d0389e27319a9a8026eae62593991939dbae1a Mon Sep 17 00:00:00 2001 From: rachaelrenk Date: Thu, 4 Jun 2026 15:38:17 +0000 Subject: [PATCH] Add internal cross-links between agent scheduling, monitoring, and trigger docs Adds 4 internal links across 2 pages, guided by the Peec AEO snapshot for agents/cloud-agents/orchestration (2026-05-05 to 2026-06-04) and Google Search Console data for docs.warp.dev/agent-platform/cloud-agents. Scheduled Agents page: - Link to Agent Management Panel and cloud agent session sharing from the execution model section so readers can find run review surfaces. - Link 'triggered cloud agents' to the Integrations overview in the comparison section. Agents page: - Link 'Runs view' and 'individual run detail pages' in the product surfaces section to their respective docs pages. Co-Authored-By: Oz --- src/content/docs/agent-platform/cloud-agents/agents.mdx | 2 +- .../agent-platform/cloud-agents/triggers/scheduled-agents.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/agent-platform/cloud-agents/agents.mdx b/src/content/docs/agent-platform/cloud-agents/agents.mdx index dced2a72..9c073194 100644 --- a/src/content/docs/agent-platform/cloud-agents/agents.mdx +++ b/src/content/docs/agent-platform/cloud-agents/agents.mdx @@ -58,7 +58,7 @@ When a team is over its plan limit (for example, after downgrading), the extra a * **Agents page** - The Agents page in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) is where teams view, create, edit, and delete cloud agents. * **Agent picker** - Forms that start a new run or schedule include an **Agent** dropdown. **Quick run** is the default (runs execute as the calling user); picking a cloud agent runs as the cloud agent instead. -* **Run filters and detail** - The Runs view lets you filter by cloud agent, and individual run detail pages show which agent executed the run. +* **Run filters and detail** - The [Runs view](/agent-platform/cloud-agents/managing-cloud-agents/) lets you filter by cloud agent, and [individual run detail pages](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) show which agent executed the run. * **Admin Panel** - Billing usage in the [Admin Panel](/knowledge-and-collaboration/admin-panel/) attributes credits consumed by cloud agent runs to the team rather than to a person. ## Related pages diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx b/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx index a703ecb3..11bb326d 100644 --- a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx +++ b/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx @@ -281,7 +281,7 @@ Each scheduled run behaves like a standard cloud agent run, with a few important * Runs execute automatically without human intervention. * All usage is billed to the team’s shared credit balance. -If a scheduled run fails, it does not block future runs. Each execution is independent. Use the [API error reference](/reference/api-and-sdk/troubleshooting/errors/) to interpret any returned error code. +If a scheduled run fails, it does not block future runs. Each execution is independent. Use the [API error reference](/reference/api-and-sdk/troubleshooting/errors/) to interpret any returned error code. To review what a scheduled run did, use the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) to find the run by status or trigger, then open the session with [cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) to inspect the prompt, commands, logs, and output. ### Permissions and responsibility @@ -300,6 +300,6 @@ Carefully review prompts and schedules before deploying them broadly, especially Scheduled Agents are best when work should happen on a predictable cadence. -If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use triggered cloud agents instead. +If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use [triggered cloud agents](/agent-platform/cloud-agents/integrations/) instead. Many teams use both together: triggers for reactive workflows, and Scheduled Agents for proactive maintenance.