diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx index 1f265b06..dd46a026 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx @@ -35,3 +35,4 @@ Use the setup walkthrough below for a quick look at how environments connect to * [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/) - Run agents from CI workflows and repository events. * [GitLab](/agent-platform/cloud-agents/integrations/gitlab/), [Bitbucket](/agent-platform/cloud-agents/integrations/bitbucket/), and [Azure DevOps](/agent-platform/cloud-agents/integrations/azure-devops/) - Connect non-GitHub repositories with tokens and Warp-managed secrets. * [AWS, GCP, and other cloud providers](/agent-platform/cloud-agents/integrations/cloud-providers/) - Give cloud agents short-lived access to cloud services. +* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Monitor and review integration-triggered runs across your team by source, status, or creator. diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx b/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx index 9fae1b70..cf13dc1c 100644 --- a/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx +++ b/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx @@ -17,3 +17,5 @@ If you're choosing between schedules, Slack, Linear, GitHub Actions, the Oz CLI, * **[CLI](/reference/cli/)** - Trigger cloud agents directly from your terminal using the Oz CLI. * **[API & SDK](/reference/api-and-sdk/)** - Programmatically trigger agents via the Warp API or SDK. * **[Integrations](/agent-platform/cloud-agents/integrations/)** - Trigger agents from external services like Slack, Linear, or GitHub Actions. + +After a trigger fires, track and review the resulting runs across your team from the [Agent Management Panel and Oz web app Runs page](/agent-platform/cloud-agents/managing-cloud-agents/), where you can filter by source, status, day, or creator. 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/).