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

# Recurring tasks

> Run a project task on a schedule, choose where it runs and what it may do, and keep it healthy.

A **Loop**, shown in a project as a recurring task, runs a project task on a schedule. Start one with `/loop`, the **Repeat** control above the composer, or **Set up a recurring task** in getting-started help. Then provide:

* a short task name;
* what the AI agent should do every time;
* a cadence (every day, every weekday, weekly, or a custom five-field cron schedule);
* the agent it **Runs with**: the Cloud agent or Codex or Claude Code on a connected computer;
* **Default permissions** for its runs: **Ask first**, **Plan only**, **Auto**, or **Full access**; and
* a **Budget per run**.

The form uses your browser’s time zone. Schedules may run at most once per hour, and AgentVille allows up to five active recurring tasks. The project's **Recurring tasks** section lets you edit, pause, or resume each one. A recurring task that fails three times in a row pauses itself and appears as needing you; resume it after correcting the underlying problem.

New and older recurring tasks default to **Ask first**. In that mode, work can continue until an action needs approval, then the run waits and appears as needing you. **Plan only** allows inspection and planning but no changes. **Full access** allows the agent to act without asking, so use it only when the task and workspace are safe for unattended changes. **Default permissions** apply to future runs. Each run starts with that default, then behaves like a normal agent chat with its own permissions setting: you may change it while the run is active without changing the default. For local agents, Auto uses that agent's own auto mode, and Full access requires a local opt-in on that computer. Editing the default does not rewrite a running occurrence, and the next occurrence starts from the latest default. Any approval already waiting is still a specific request and needs an explicit answer.

Choosing Codex or Claude Code keeps the schedule in AgentVille's cloud but runs each occurrence, with the selected permissions, on the selected computer and folder. If that computer or agent connection is offline, on a different machine, or no longer exposes the folder, that occurrence fails; AgentVille does not move it to the Cloud agent. Choosing the Cloud agent keeps execution in AgentVille's cloud.

Use a recurring task for concrete repeating work, such as a weekday inbox triage, a weekly project update, or a daily review through a plugin you connected. Keep one-off explorations as normal project work.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.