# Schedules

A schedule saves a task and its timing so you do not have to repeat the request manually. Each occurrence starts a fresh conversation under current permissions, configuration, and funding.

To summarize feedback every Friday, schedule a Chat. To prepare a brief, pause for approval, and collect the reviewed result every Friday, [schedule a Workflow](/docs/workflows/access).

Write the task so it can stand on its own. Include the information to use, the period to cover, and the result you expect.

## Where scheduled work runs

| Owner | New occurrence | Context |
| --- | --- | --- |
| Agent | A fresh Agent conversation. | The Agent's authorized configuration and resources. |
| Chat schedule | A fresh Chat and conversation. | Eligible Workspace configuration. |
| Project | A fresh Project conversation. | The Project's authorized development context. |

Chat schedules are private to their creator within the Workspace. Agent and Project schedules belong to those resources. The original conversation records where the request came from; later occurrences do not continue that transcript.

A fresh conversation also does not mean a fresh copy of shared Agent or Project files. See [Conversations](/docs/concepts/conversations).

## Example: a weekly support summary

A useful instruction names the evidence and the output:

> Summarize customer issues from the previous Monday through Sunday using the authorized support connection. Group recurring problems, link to the source records, and save a report for review. Identify missing or inaccessible evidence. Do not send messages to customers.

Choose the supported timing in the scheduling workflow and review the timezone. Verify the relevant [connection](/docs/configuration/connections) and supply any required references or attachments explicitly. “Do that again” is not enough context for a fresh occurrence.

Before relying on the recurring task, review a representative result. Confirm that it uses the intended period, cites the right evidence, and produces the expected file.

## Review and stop recurring work

Inspect each occurrence's conversation, saved result, and [usage](/docs/billing/usage). Current authorization still applies: a saved schedule does not preserve access to a connection indefinitely.

Pause or remove the schedule when you want recurring work to end. Archiving or deleting its creation conversation does not remove the independent schedule. Review schedules when credentials change or a resource is retired; see [Agent lifecycle](/docs/agents/lifecycle) and [Project lifecycle](/docs/projects/lifecycle).

Use [Budgets](/docs/billing/budgets) to constrain new chargeable work. Budget changes do not undo completed actions or guarantee that all active work stops immediately.

## Schedules or Jobs

Use a schedule for recurring Operator work with a conversational result, such as the weekly support report. Use [Jobs](/docs/services/jobs) for application background behavior, such as processing an uploaded file or generating an application export.

Production Jobs run in the Site's application context. A Project schedule does not implicitly release software or gain production credentials.