openclaw - 💡(How to fix) Fix [Feature]: Support native callback endpoints for external script integration

I would like to request a native "Callback Endpoint" feature in the OpenClaw runtime.

Fix / Workaround

I am currently running Python scripts inside the same container as the OpenClaw runtime. My goal is to have these scripts notify the OpenClaw agent immediately upon completion or failure (e.g., a data fetching script fails and needs the agent to analyze the error). Currently, OpenClaw does not natively expose a local callback endpoint (like a simple HTTP POST listener) for external scripts to push notifications. The existing workarounds involve: 1.Using a cron job to poll a file directory (which introduces latency and unnecessary resource consumption). 2.Running a separate, self-managed lightweight HTTP server just to bridge the communication, which adds complexity to the container's process management.

Affected users/systems/channels: Developers and automation engineers running OpenClaw in containerized environments (e.g., Docker) who need to integrate external Python scripts or CLI tools with the agent. Severity: Blocks efficient workflow. While workarounds exist, they force developers to implement fragile, non-standard architectural patterns (like file-based IPC or custom middleware) instead of using a robust, built-in integration method. Frequency: Always. Every time an external script needs to report a status (especially failures or urgent events) back to the agent, this limitation is encountered. Consequence: 1.High Latency: Relying on cron-based file polling introduces unavoidable delays (e.g., 1-minute intervals), making real-time error handling impossible. 2.Resource Waste: Continuous polling consumes unnecessary CPU cycles and I/O resources even when no events occur. 3.Increased Complexity: Developers are forced to maintain separate, self-managed HTTP servers or complex file-locking mechanisms just to 4.bridge simple communications, increasing the risk of bugs and maintenance overhead.