Scheduled Agents quickstart

Scheduled agents are cloud agents that run on a recurring cron schedule, handling recurring tasks automatically without manual triggers. This guide walks you through setting up an agent that triages your GitHub bug reports every week, checks whether each issue has enough detail to investigate, and posts follow-up comments when information is missing. You’ll use a prebundled skill and the Oz web app; no CLI or custom code required.

Watch this short demo of creating and testing a scheduled agent:

---

Prerequisites

• A Warp account on an eligible plan - Build, Max, or Business, with credits available. See Access, Billing, and Identity.
• A cloud environment - Agents run inside a configured environment that includes repos and other dependencies. If you don’t have one, follow the Cloud Agents Quickstart to create one first.

---

1. Set up a scheduled agent

1. From the Schedules page in the Oz web app, click New schedule.
2. Enter a schedule name, e.g. Weekly bug report triage.
3. Under Agent, choose the identity the schedule runs as. Quick run is the default and runs every execution as you. See Who the schedule runs as before you decide.
4. Under Skills, select github-bug-report-triage.
5. Choose your environment.
6. Under Frequency, choose a preset or enter a custom cron expression (e.g., 0 9 * * 1 for every Monday at 9 AM).
7. Click Create schedule.

Breaking it down: The schedule lives in Oz’s cloud infrastructure. Unlike a local cron job, it fires even when your machine is off. Each run starts a fresh, isolated session with no state carried over from previous executions, and every run is tracked and reviewable in the Oz web app.

Who the schedule runs as

The Agent setting controls the identity behind every run, which determines how the agent authenticates to GitHub:

• Quick run (default) - Runs execute as the user who created the schedule, using that person’s GitHub credentials. Pull requests the agent opens are authored by that person.
• A cloud agent - Runs execute as that cloud agent. With team GitHub authorization configured, the agent authenticates as the Oz by Warp GitHub App, so pull requests are authored by the app instead of an individual.

Choose a cloud agent for any schedule that opens pull requests. Bot-authored PRs are clearly attributable to automation, and they can be reviewed and approved by anyone on the team — including the person who created the schedule, who cannot approve a PR authored by their own account.

Caution

The Agent setting has no equivalent flag in the Oz CLI, so a schedule created with oz schedule create always runs as the user who created it. To run it as a cloud agent, set Agent on the schedule in the Oz web app after creating it.

---

2. Watch your first run

To verify your setup without waiting for the schedule to fire, trigger a test run now:

1. From the Schedules page in the Oz web app, click the schedule you just created.
2. Click ⋮ and select Run now, then click Run to confirm.

Your test run will appear under All on the Runs page. Once the schedule fires on its cron, those runs will appear under Recurring.

Runs are also accessible from the conversation panel view in the Warp app and on mobile via the Oz web app.

Note

Prefer the CLI? See Scheduled Agents for oz schedule create, oz schedule list, and full schedule management commands. To use a custom skill instead of a prebundled one, see Skills as Agents.

---

Next steps

• Choose the right unattended trigger - Compare schedules, Slack, Linear, GitHub Actions, CLI, and API workflows in Run agents unattended with schedules and triggers.
• Trigger agents from your tools - Connect Oz to Slack or Linear to trigger agents from mentions or issue updates. See Integrations Quickstart.
• Manage and refine your schedule - Change the frequency, swap skills, or pause and resume the schedule. See Scheduled Agents for the full reference.
• Share with your team - Schedules and environments are shared across your Warp team, so everyone benefits automatically.