1.4 KiB
10 OpenClaw Tips for Daily Use
- Tip 1: Use memory_search before every memory-dependent task
- Tip 2: Batch similar operations to reduce token burn
- Tip 3: Create skills for repeated workflows
- Tip 4: Use subagents for parallel tasks
- Tip 5: Heartbeat is for batches, cron is for schedules
- Tip 6: Commit before every edit
- Tip 7: Use browser automation carefully
- Tip 8: Platform formatting matters
- Tip 9: Gateway config changes are immediate
- Tip 10: Silence costs nothing
Tip 1: Use memory_search before every memory-dependent task
Always search your memory bank before answering questions about prior work. This maintains continuity and prevents re-asking.
Tip 2: Batch similar operations to reduce token burn
Group file reads, web searches, and git operations. Each tool call has overhead—combine them.
Tip 3: Create skills for repeated workflows
If you do the same task 3+ times, make it a skill. Future-you will thank you.
Tip 4: Use subagents for parallel tasks
Spawn subagents for independent work. You handle 4-8 concurrently. Don't let tasks block.
Tip 5: Heartbeat is for batches, cron is for schedules
Heartbeat = check multiple things in context. Cron = exact timing or isolation. Choose wisely.
Tip 6: Commit before every edit
Use `git commit` before and after changes. Traceability beats speed.
Tip 7: Use browser automation carefully
Browser snapshots are powerful but expensive. Web fetch is cheaper for reading. Match tool to task.
Tip 8: Platform formatting matters
No tables on Discord/WhatsApp. Wrap Discord links in `< >`. Know your audience.
Tip 9: Gateway config changes are immediate
Every `gateway config.patch` restarts the system. Plan accordingly.
Tip 10: Silence costs nothing
Use `NO_REPLY` when you have nothing to say. Quality over quantity.