Summary

When an isolated cron job agent response includes [[reply_to_current]] tag, the delivery shows delivered: true but the message is never actually sent to Telegram.

Environment

• OpenClaw Version: 2026.2.26
• Channel: Telegram
• Cron config: sessionTarget: "isolated", delivery.mode: "announce"

Steps to Reproduce

1. Create an isolated cron job with announce delivery:

openclaw cron add \
  --name "test-reply-tag" \
  --at "2026-02-28T10:00:00+08:00" \
  --message "Test reminder message" \
  --session isolated \
  --announce \
  --channel telegram \
  --to "<chat_id>" \
  --delete-after-run

2. When the cron executes, if the agent includes [[reply_to_current]] in its response, the message is silently dropped

Expected Behavior

• Either: [[reply_to_current]] should be automatically stripped in isolated sessions (no inbound message to reply to)
• Or: Delivery should fail with an explicit error instead of showing delivered: true

Actual Behavior

• Session transcript shows agent response with [[reply_to_current]] tag
• Cron run record shows delivered: true, deliveryStatus: "delivered"
• Telegram message is never received

Evidence

Working cron (no reply tag):

{"text":"收到测试消息 ✅\n\nCron 任务投递正常..."}

→ Message delivered successfully ✅

Failing cron (with reply tag):

{"text":"[[reply_to_current]] 🐟 **面试提醒**\n\n⏰ 10分钟后有面试！..."}

→ Shows delivered: true but message never arrives ❌

Suggested Fix

In isolated cron sessions, automatically strip [[reply_to_current]] and [[reply_to:<id>]] tags before delivery, since there is no inbound message context to reply to.

Workaround

Add explicit instruction in cron prompt: 注意：不要使用 [[reply_to_current]] 标签。