Summary

When delivery.mode: "announce" sends a cron job's response text to a chat channel, the responsePrefix (e.g. [Thames]) is not applied to the message. Interactive replies correctly resolve responsePrefix: "auto" via resolveIdentityNamePrefix(), but cron delivery sends raw response text.

This means cron-delivered messages arrive without the agent name prefix, making it unclear which agent sent the message — especially in group chats where multiple agents deliver to the same channel.

Steps to Reproduce

1. Configure responsePrefix: "auto" (global or per-channel)
2. Create a cron job with delivery.mode: "announce" targeting a WhatsApp group
3. The agent's identity has a name field (e.g. "Thames")
4. When the cron job runs, the delivered message does not include the [Thames] prefix

Expected Behaviour

Cron announce delivery should apply the same responsePrefix logic as interactive replies — prepending [{identity.name}] when responsePrefix: "auto".

Current Workaround

Adding "Begin your response with [AgentName]" to the cron payload message. This works but is fragile (depends on LLM compliance) and duplicates logic that the framework should handle.

Environment

• OpenClaw 2026.2.26 (bc50708)
• macOS Darwin 25.3.0 arm64