OpenClaw Auto-Reply Lifecycle Builder
Configure how OpenClaw notifies users when agents stop, rotate, or restart. Build per-channel reply rules with custom messages, delays, and fallbacks — then export a ready-to-use YAML config. Based on OpenClaw PR #61267 that unified the reply lifecycle.
Why Use the Auto-Reply Lifecycle Builder
Inspired by the unified reply lifecycle shipped in OpenClaw PR #61267 on April 5, 2026.
Unified Lifecycle Events
Configure replies for all three lifecycle phases — stop, rotation, and restart — in one place, matching the unified model from OpenClaw PR #61267.
Per-Channel Customization
Tailor auto-reply messages for each channel: Discord, Slack, Telegram, Matrix, Web UI, and WhatsApp. Different audiences, different tones.
Delay & Silent Modes
Set per-event delays to avoid premature messages during restarts, or enable silent mode to suppress replies entirely for specific events.
Fallback Messages
Define fallback text for when the primary message fails to send — covering rate limits, network errors, and channel-specific delivery quirks.
Live Flow Preview
See a visual timeline of how auto-replies fire across stop, rotation, and restart events before you deploy the config.
One-Click YAML Export
Copy the generated YAML config and paste it directly into your OpenClaw config.yaml. No manual formatting needed.
Build Your Auto-Reply Config
Select channels, customize messages for each lifecycle event, and copy the YAML when you're done.
Frequently Asked Questions
What is the auto-reply lifecycle in OpenClaw?
The auto-reply lifecycle governs how OpenClaw sends status messages when an agent changes state. There are three events: stop (agent finishes or is halted), rotation (agent is swapped for a different model or instance), and restart (agent crashes and recovers). PR #61267 unified these into a single, consistent configuration model.
Why were stop, rotation, and restart unified?
Before PR #61267, each lifecycle event had its own independent reply logic with slightly different behavior. This led to inconsistent user experiences — for example, rotation messages might arrive before the old agent's final reply finished sending. The unified model ensures consistent ordering, deduplication, and timing across all three events.
Can I configure different messages per channel?
Yes. Each channel (Discord, Slack, Telegram, Matrix, Web UI, WhatsApp) can have its own message, delay, and fallback for every lifecycle event. This lets you match each platform's tone — brief for Telegram, detailed for Slack, etc.
What does silent mode do?
Silent mode suppresses the auto-reply entirely for a specific event on a specific channel. The lifecycle event still occurs internally, but no message is sent to users. This is useful for rotation events on channels where a seamless switch is preferred.
How does the delay setting work?
The delay setting adds a configurable pause (0–30 seconds) before sending the auto-reply. This is especially useful for restart events: a short delay prevents sending 'restarting...' messages for transient hiccups that resolve in under a second.
Where do I paste the generated YAML?
Copy the generated YAML and paste it into your OpenClaw config.yaml file under the top-level auto_reply key. If you're using DeployClaw, you can paste it into the Config Editor in the dashboard — it will be validated and applied on the next agent restart.