From f124bfacd205ed1f513c2019a162ad08a98a814f Mon Sep 17 00:00:00 2001 From: rachaelrenk Date: Mon, 15 Jun 2026 09:04:38 +0000 Subject: [PATCH] docs: add AEO cross-links for agents and orchestration Add high-confidence internal cross-links for the agents, cloud agents, and orchestration topic area, grounded in Peec AEO signals (scheduling, managing and observing multiple agents) and existing docs: - Scheduled Agents reference now links to the Scheduled Agents quickstart for a guided, no-CLI setup path. - Run multiple agents at once guide now links to Agent notifications and the Agent Management Panel for notification setup and run observability. Co-Authored-By: Oz --- .../agent-platform/cloud-agents/triggers/scheduled-agents.mdx | 2 ++ .../running-multiple-agents-at-once-with-warp.mdx | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) 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 a6f7f11b..9bc88ecd 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 @@ -14,6 +14,8 @@ Warp's Scheduled Agents let you run cloud agents automatically on a **recurring Scheduled Agents run in the background on Warp’s infrastructure. Each run starts from a clean session, executes a fixed prompt, and produces its own task and session history that can be inspected after the fact. +For a guided, no-CLI walkthrough that creates a recurring agent from the Oz web app, see the [Scheduled Agents quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/). This page is the full reference for managing schedules with the Oz CLI. + If you're deciding whether to use a schedule, Slack or Linear trigger, GitHub Actions, the Oz CLI, or the API, see [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/). --- diff --git a/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx b/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx index b20db6fe..f5f8ca93 100644 --- a/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx +++ b/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx @@ -29,7 +29,7 @@ Each agent runs in its own thread, complete with: * Notifications when blocked or completed * Separate command histories -Because Warp is a desktop app, it can send system notifications to alert you when an agent finishes or when it needs review. +Because Warp is a desktop app, it can send system notifications to alert you when an agent finishes or when it needs review. To set up notifications for Claude Code, Codex, and OpenCode, see [Agent notifications](/agent-platform/capabilities/agent-notifications/). --- @@ -94,6 +94,6 @@ Open the Agent Mode Dashboard to see: * Completed tasks * Logs and outputs -You can refine or cancel tasks mid-run if needed, or switch back to manual commands. +You can refine or cancel tasks mid-run if needed, or switch back to manual commands. To track these runs across your account and team, including cloud agent runs, open the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app. For a workflow-oriented setup guide that covers task decomposition, worktrees, cloud orchestration, validation, and review handoff, see [How to run multiple AI coding agents](/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/).