let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: expand cron jobs guidance

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-11 10:57:30 +00:00
parent 2ebad5af1c
commit 28b25e8abb
1 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
docs/automation/cron-jobs.md
View File

@@ -64,6 +64,23 @@ Key behaviors:
Use isolated jobs for noisy, frequent, or "background chores" that shouldn't spam Use isolated jobs for noisy, frequent, or "background chores" that shouldn't spam
your main chat history. your main chat history.
### Payload shapes (what runs)
Two payload kinds are supported:
- `systemEvent`: main-session only, routed through the heartbeat prompt.
- `agentTurn`: isolated-session only, runs a dedicated agent turn.
Common `agentTurn` fields:
- `message`: required text prompt.
- `model` / `thinking`: optional overrides (see below).
- `timeoutSeconds`: optional timeout override.
- `deliver`: `true` to send output to a provider target.
- `provider`: `last` or a specific provider.
- `to`: provider-specific target (phone/chat/channel id).
- `bestEffortDeliver`: avoid failing the job if delivery fails.
Isolation options (only for `session=isolated`):
- `postToMainPrefix` (CLI: `--post-prefix`): prefix for the summary system event in main.
### Model and thinking overrides ### Model and thinking overrides
Isolated jobs (`agentTurn`) can override the model and thinking level: Isolated jobs (`agentTurn`) can override the model and thinking level:
- `model`: Provider/model string (e.g., `anthropic/claude-sonnet-4-20250514`) or alias (e.g., `opus`) - `model`: Provider/model string (e.g., `anthropic/claude-sonnet-4-20250514`) or alias (e.g., `opus`)
@@ -86,6 +103,10 @@ Isolated jobs can deliver output to a provider. The job payload can specify:
If `provider` or `to` is omitted, cron can fall back to the main session’s “last route” If `provider` or `to` is omitted, cron can fall back to the main session’s “last route”
(the last place the agent replied). (the last place the agent replied).
Target format reminders:
- Slack/Discord targets should use explicit prefixes (e.g. `channel:<id>`, `user:<id>`) to avoid ambiguity.
- Telegram topics should use the `:topic:` form (see below).
#### Telegram delivery targets (topics / forum threads) #### Telegram delivery targets (topics / forum threads)
Telegram supports forum topics via `message_thread_id`. For cron delivery, you can encode Telegram supports forum topics via `message_thread_id`. For cron delivery, you can encode
the topic/thread into the `to` field: the topic/thread into the `to` field:
@@ -176,6 +197,14 @@ Manual run (debug):
clawdbot cron run <jobId> --force clawdbot cron run <jobId> --force
``` ```
Edit an existing job (patch fields):
```bash
clawdbot cron edit <jobId> \
--message "Updated prompt" \
--model "opus" \
--thinking low
```
Run history: Run history:
```bash ```bash
clawdbot cron runs --id <jobId> --limit 50 clawdbot cron runs --id <jobId> --limit 50