Skip to content

docs: add AEO cross-links for agents and orchestration #228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rachaelrenk wants to merge 2 commits into
base: main
Choose a base branch
from
+4 −2
Open

docs: add AEO cross-links for agents and orchestration #228

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f124bfa
docs: add AEO cross-links for agents and orchestration
rachaelrenk Jun 15, 2026
11afd0f
Merge branch 'main' into docs/aeo-crosslinks-agents-orchestration-202…
rachaelrenk Jun 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/).

---
Expand Down
4 changes: 2 additions & 2 deletions ...ntent/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/).

---

Expand Down Expand Up @@ -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/).
Loading