Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ Use this when you want Oz to run agent workloads on Warp-managed infrastructure,

#### Common ways to trigger

* **First-party integrations (Slack, Linear, etc.)** that create tasks automatically from external events.
* **First-party integrations** (Slack, Linear, etc.) that create tasks automatically from external events. See the [Integrations overview](/agent-platform/cloud-agents/integrations/).
* **Scheduled agents** for recurring work (cron-like automation).
* **Custom triggers** from your own systems using Warp’s API/SDK.
* **On-demand cloud jobs** using CLI commands like `oz agent run-cloud`.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -101,8 +101,8 @@ In addition to Warp's built-in agent, Warp provides first-class support for thir
The same agent capabilities that power interactive conversations in Warp also run in the cloud. Cloud agents can:

* React to events from Slack, Linear, or GitHub
* Run on schedules for recurring tasks like dependency updates
* Execute in parallel across repos or tasks
* Run on [schedules](/agent-platform/cloud-agents/triggers/scheduled-agents/) for recurring tasks like dependency updates
* Execute [in parallel across repos or tasks](/agent-platform/cloud-agents/orchestration/)
* Produce tracked, auditable, shareable runs

Cloud agents are ideal for work that doesn't need your immediate attention—PR reviews, issue triage, routine maintenance, and integration-driven workflows.
Expand Down
Loading