jb/paseo
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Document workspace-first agent automation (#2192)

Browse Source 
* docs: explain workspace-first automation

* docs: make automation examples self-contained
This commit is contained in:
Mohamed Boudra
2026-07-18 15:18:05 +02:00
committed by GitHub
parent 05d1f838d8
commit 72752b7db6
12 changed files with 237 additions and 96 deletions
Download Patch File Download Diff File Expand all files Collapse all files
public-docs/schedules-cli.md
+21 -7
View File
@@ -8,7 +8,7 @@ category: Schedules
# Schedules from the CLI
`paseo schedule` creates and manages [schedules](/docs/schedules) from your terminal, useful for headless boxes and scripts.
`paseo schedule` creates and manages new-agent [schedules](/docs/schedules) from your terminal, useful for headless boxes and scripts. Every run starts a fresh agent.
## Create
@@ -62,16 +62,28 @@ paseo schedule create \
"Review overnight CI failures and summarize anything urgent."
```
Heartbeat the current agent:
## Heartbeats
Inside a running Paseo agent, create a heartbeat for that same conversation:
```bash
paseo schedule create \
--every 20m \
--target self \
paseo heartbeat create \
--cron "*/20 * * * *" \
--name heartbeat \
"Check the current task state and continue with the next useful step."
```
The heartbeat interface is deliberately small:
```bash
paseo heartbeat update <id> --cron "*/10 * * * *"
paseo heartbeat delete <id>
```
Updating a heartbeat changes only its cron cadence and optional time zone. Its target and prompt stay fixed. Heartbeat commands require `PASEO_AGENT_ID`, which Paseo sets inside agent sessions.
Heartbeats require a raw `--cron` expression. The `--every` presets below are available only for new-agent schedules.
## Manage
```bash
@@ -87,8 +99,10 @@ paseo schedule delete <id>
## Cadence
Use `--every <duration>` for intervals and `--cron "<expr>"` for 5-field cron. Cron schedules default to UTC. Pass `--timezone <IANA>` to interpret cron fields in a local wall-clock time zone, for example `--timezone America/New_York`. The persisted `nextRunAt` is still a UTC instant, but it is computed from that local time zone so recurring jobs stay at the same local time across daylight saving time changes.
Use `--cron "<expr>"` for a 5-field cron expression. For common cron-compatible cadences, `--every <duration>` accepts presets such as `5m` or `1h` and compiles them to cron. It does not create a rolling interval anchored to creation time.
Interval schedules run once immediately by default; pass `--no-run-now` to wait for the first interval. Cron schedules wait for the next matching time; pass `--run-now` to fire once immediately.
Schedules default to UTC. Pass `--timezone <IANA>` to interpret cron fields in a local wall-clock time zone, for example `--timezone America/New_York`. The persisted `nextRunAt` is still a UTC instant, but it is computed from that local time zone so recurring jobs stay at the same local time across daylight saving time changes.
Schedules wait for the next matching cron time by default. Pass `--run-now` to start one immediate run on creation.
When targeting a remote daemon with `--host`, pass `--cwd`; your local working directory may not exist on the remote machine.