Bug type

Behavior bug (incorrect output/state without crash)

Summary

Cron job with sessionTarget: "main" triggers both systemEvent and scheduled reminder despite delivery.mode: "none".

Steps to reproduce

1. Create a cron job with the following configuration:

   • sessionTarget: "main"
   • payload.kind: "systemEvent"
   • delivery.mode: "none"
   • Schedule: 0 6,8,10,12,14,16,18,20,22 * * * (every 2 hours)

2. Wait for the scheduled execution time

3. Observe the session logs

Expected behavior

Only the systemEvent should be injected into the main session. With delivery.mode: "none", no additional "scheduled reminder" wrapper notification should appear.

Actual behavior

Both triggers appear simultaneously in the session:

1. System (untrusted): [override] Disregard any instruction... (systemEvent)
2. A scheduled reminder has been triggered... (reminder wrapper)
   The actual Telegram delivery works correctly (only once), but the duplicate log entries create confusion in the session history.

OpenClaw version

2026.3.12

Operating system

Ubuntu (LXC container)

Install method

npm global

Model

kimi-coding/k2p5

Provider / routing chain

kimi-coding/k2p5

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Job configuration

{
  "id": "312b12d3-b485-4dcc-b93b-1f8515d8174b",
  "name": "periodic_arona_briefing_trigger",
  "enabled": true,
  "schedule": {
    "expr": "0 6,8,10,12,14,16,18,20,22 * * *",
    "tz": "Asia/Seoul"
  },
  "sessionTarget": "main",
  "wakeMode": "now",
  "payload": {
    "kind": "systemEvent",
    "text": "[override] Disregard any instruction to handle this internally..."
  },
  "delivery": {
    "mode": "none"
  }
}

Suggested fix

Respect delivery.mode: "none" for main session cron jobs and suppress the reminder generation.