Self-Prompt: Forcing Agent Responses

The Problem

When automated scripts (cron, monitoring) send messages via openclaw message send:

• - Messages appear in chat as "system messages"
• Agents may treat them as background info, not tasks
• Agents respond to user messages but ignore automated ones
• Accountability checks, alerts, and tasks go unanswered

The Solution

Use openclaw agent instead of openclaw message send for messages requiring agent response:

CODEBLOCK0

Why This Works

• - openclaw message send → Creates chat message → Agent sees as "notification"
• INLINECODE4 → Triggers actual agent turn → Agent MUST process and respond

Quick Start

For Bash Scripts

Use scripts/send_agent_task.sh:

CODEBLOCK1

For Python Scripts

Use scripts/send_agent_task.py:

CODEBLOCK2

Pattern: Data + Task Separation

For monitoring scripts, separate data delivery from task requests:

CODEBLOCK3

Common Use Cases

Accountability Checks

Monitoring Alerts

Scheduled Research Tasks

Session Key Format

The session key follows this pattern:
CODEBLOCK7

Examples:

• - INLINECODE7
• INLINECODE8
• INLINECODE9

Script Reference

sendagenttask.sh

CODEBLOCK8

• - Sends task via INLINECODE11
• Captures response
• Sends response to group via INLINECODE12
• Logs to INLINECODE13

sendagenttask.py

CODEBLOCK9

Troubleshooting

Agent not responding

• - Verify agent is running: INLINECODE15
• Check session key format matches your agent/group
• Increase timeout for long-running tasks

Response not appearing in chat

• - Ensure script sends response via message send after capturing
• Check GROUP_ID is correct (negative for groups)
• Verify channel is correct (telegram/discord/etc)

Timeout errors

• - Increase timeout for research/analysis tasks (300-600 seconds)
• Check if agent is overloaded with concurrent requests