vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 17:50:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(cron): keep pairing approvals out of automation recipients

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-02 08:02:58 +01:00
parent 221ad94f18
commit 53c4217110
9 changed files with 43 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -164,6 +164,8 @@ For isolated jobs, chat delivery is shared. If a chat route is available, the ag
When an agent creates an isolated reminder from an active chat, OpenClaw stores the preserved live delivery target for the fallback announce route. Internal session keys may be lowercase; provider delivery targets are not reconstructed from those keys when current chat context is available.
Implicit announce delivery uses configured channel allowlists to validate and reroute stale targets. DM pairing-store approvals are not fallback automation recipients; set `delivery.to` or configure the channel `allowFrom` entry when a scheduled job should proactively send to a DM.
Failure notifications follow a separate destination path:
- `cron.failureDestination` sets a global default for failure notifications.

1
docs/channels/whatsapp.md
View File

@@ -219,6 +219,7 @@ content and identifiers.
Runtime behavior details:
- pairings are persisted in channel allow-store and merged with configured `allowFrom`
- scheduled automation and heartbeat recipient fallback use explicit delivery targets or configured `allowFrom`; DM pairing approvals are not implicit cron or heartbeat recipients
- if no allowlist is configured, the linked self number is allowed by default
- OpenClaw never auto-pairs outbound `fromMe` DMs (messages you send to yourself from the linked device)