Automating OpenClaw Startup with BOOT.md

I often find myself repeating the same setup steps every time I launch a development tool. It is frustrating to manually toggle settings or send initial pings when the software could just do it for me. I prefer a setup that knows its job from the second it starts so I can get straight to work.

What You’ll Need

• OpenClaw access
• A text editor to create your configuration file

Quick Start

You can define exactly what OpenClaw does when it boots by using a BOOT.md file. Follow these steps to get it running in under five minutes:

1. Create a file named BOOT.md in your environment.
2. Write short, explicit instructions for the startup sequence.
3. Include a command to enable hooks.internal.enabled.
4. If your task sends a message, use the message tool and then reply with NO_REPLY.

# Startup Instructions
Enable hooks.internal.enabled.
Use the message tool to send a greeting, then reply with NO_REPLY.

Troubleshooting

• Task hangs after sending a message: You must reply with NO_REPLY after using the message tool to finish the sequence.
• Internal hooks are disabled: Ensure your BOOT.md explicitly includes the instruction to enable hooks.internal.enabled.

If you run into other issues, the AI Setup Assistant can help you get back on track.

What’s Next

• OpenClaw Hooks Documentation
• Message Tool Reference