> ## Documentation Index
> Fetch the complete documentation index at: https://getskydive.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Routines

> Recurring and future-triggered work, no human in the loop

Agents can run on their own schedule. Use routines for anything that should happen **later** or **repeatedly**.

<img src="https://mintcdn.com/skydive/2VR7bKqFZZqW4hyR/images/agents/scheduled-runs-penny.png?fit=max&auto=format&n=2VR7bKqFZZqW4hyR&q=85&s=8fd3d66392a319fb36a348e911ec4e21" alt="Penny setting a recurring routine" style={{borderRadius:'12px',marginBottom:'8px'}} width="1600" height="992" data-path="images/agents/scheduled-runs-penny.png" />

## What you can schedule

<CardGroup cols={2}>
  <Card title="Recurring work" icon="repeat">
    "Every weekday at 9am, summarize what changed in our shared inbox."
  </Card>

  <Card title="A one-time future task" icon="calendar-day">
    "Remind me at 5pm to send the invoice."
  </Card>

  <Card title="Periodic checks" icon="magnifying-glass-chart">
    "Every Monday, check our competitors' pricing pages and flag changes."
  </Card>

  <Card title="Reports & digests" icon="newspaper">
    "Send a weekly summary of closed deals every Friday afternoon."
  </Card>
</CardGroup>

## How it works

Set up a schedule by asking the agent in plain language:

```text theme={null}
Every weekday at 9am Eastern, post a summary of yesterday's support
tickets to our #cs channel.
```

The agent creates the schedule. When it fires, the run happens **with no human in the loop**. The agent acts on the instruction you gave and delivers the result to the channel you specified.

<Tip>
  Write the instruction with all the context the future run needs. No one is there to clarify. "Summarize yesterday's tickets and post to #cs" beats "do the ticket thing."
</Tip>

## Cadence and timing

* **Recurring**: on a schedule like "every weekday at 9am" or "the first of each month." Time zones are respected: "9am" means 9am where you are.
* **One-time**: a single future moment, like "tomorrow at noon" or a specific date.

## Suggested routines

You don't have to think up every schedule yourself. On the **Routines** page, your agent proposes schedules it could run for you, based on its role, its past work, and its connected services. Each suggestion is a real, tool-using task: check, post, summarize.

Open a suggestion to see what it would do and when. Click **Set it up** to turn it into a live routine, or dismiss it. Suggestions refresh on their own.

## Managing schedules

List, pause, resume, update, or cancel an agent's schedules at any time. Ask in plain language:

```text theme={null}
Pause the daily ticket summary until next week.
```

Each routine has a detail view with its full run history. Every past run links to the conversation it ran in. Open any firing to see exactly what the agent did.

## Where results go

A routine can deliver to any channel: a Slack channel, an email, or a direct message. There is no live conversation when it fires, so name the destination when you set up the schedule.

<Card title="Pair it with a skill" icon="list-check" href="/docs/agents/skills">
  Schedule a codified workflow to run a whole process automatically.
</Card>