mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-30 05:02:58 +00:00
paseo-bot[bot]
0eee4fd9b0
The schedule and worktree guides omitted the existing retention control and its default. Document the app setting and clarify that CLI and MCP tools do not expose it. Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>
46 lines
2.9 KiB
Markdown
46 lines
2.9 KiB
Markdown
---
|
|
title: Schedules
|
|
description: Run fresh agents on cron schedules or wake an existing agent with a heartbeat.
|
|
nav: Overview
|
|
order: 25
|
|
category: Schedules
|
|
---
|
|
|
|
# Schedules
|
|
|
|
A schedule starts a new agent for you on a cron cadence: at this time, run this prompt, in this repo, with these agent settings.
|
|
|
|
Paseo also has **heartbeats**. A heartbeat sends a recurring prompt back into one existing agent so it can reassess and continue the same conversation.
|
|
|
|
Both concepts use the same cron engine, but their product surfaces stay separate:
|
|
|
|
- **Schedules** create a new agent each run. You can inspect, pause, resume, run once, update, or delete them.
|
|
- **Heartbeats** target one existing agent. They are intentionally lightweight: create or delete them over MCP; from the CLI you can also update only their cron period.
|
|
|
|
Cron is the canonical cadence. The CLI accepts simple presets such as `5m` or `1h`, but compiles them to cron rather than storing a separate interval type.
|
|
|
|
Both run on a cadence you set. To start an agent from an external event instead — a comment, a mention — see [Hub](/docs/hub).
|
|
|
|
## What it's for
|
|
|
|
- **Fresh recurring jobs:** start a clean agent for daily triage, reports, or maintenance.
|
|
- **Heartbeats:** have the current agent periodically reassess state and keep moving.
|
|
- **Build babysitting:** keep one agent checking CI, EAS, Docker, or release builds until they pass.
|
|
- **Daily triage:** scan issues, PRs, and failing checks every morning.
|
|
- **Maintenance sweeps:** refresh dependencies, audit docs, or clean stale branches.
|
|
|
|
## Ways to create one
|
|
|
|
- **In the app** — open the Schedules view and create one with agent settings, a cron cadence, a repo, and a prompt. This is the main way to create and manage schedules.
|
|
- **[From chat](/docs/schedules-chat)** — ask the agent in a chat and it sets the schedule up for you.
|
|
- **[From the CLI](/docs/schedules-cli)** — `paseo schedule create`, for headless boxes and scripts.
|
|
- **[Over MCP](/docs/mcp)** — agents create and manage schedules programmatically.
|
|
|
|
## Keep run workspaces
|
|
|
|
Each new-agent schedule run creates a workspace. **Archive on finish** is on by default: when the run ends, Paseo archives that workspace and its agent. With worktree isolation, archiving also removes the worktree after its last active workspace is archived.
|
|
|
|
To keep runs available, open the schedule in the app's Schedules view, turn off **Archive on finish**, and save. Paseo keeps each run's workspace and agent active until you archive them; runs that fail before creating an agent are still cleaned up. This option also applies to local isolation; archiving a local workspace leaves the project directory in place.
|
|
|
|
The stored option is `target.config.archiveOnFinish`, a boolean that defaults to `true` when omitted. The CLI and MCP schedule tools do not expose this option; use the app to change it. Heartbeats use an existing agent and do not have this option.
|