Awesome OpenClaw Tips

Table of Contents

• 💬 Messages
  • MES-01: Enable ack reactions by setting messages.ackReactionScope
• 📨 Telegram
  • TEL-01: Use Telegram inline buttons for recurring actions
  • TEL-02: Split conversations into threads so context stops bleeding across topics
  • TEL-03: Set a system prompt per Telegram topic so /new resets noise without losing purpose
  • TEL-04: Give OpenClaw its own Telegram topic for fast admin work
• 🧠 Memory
  • MEM-01: Make your agent learn from its mistakes
  • MEM-02: Flush important state before compaction eats it
  • MEM-03: Use SQLite memory search before you pay for embeddings
  • MEM-04: Treat chat history as cache, not the source of truth
  • MEM-05: Periodically self-clean memory instead of letting it rot forever
• 🛡️ Reliability
  • REL-01: Don't put all your fallbacks on the same provider
  • REL-02: Your agent says "done" when it isn't
  • REL-03: Use heartbeat to rotate recurring checks, not just repeat one generic check
  • REL-04: Turn on tool-loop detection before a bad run burns hours
• 💸 Cost
  • COST-01: Your heartbeat model is costing you more than you think
  • COST-02: Use cache-ttl pruning or idle sessions will re-cache junk history
  • COST-03: Local models are often a false economy
  • COST-04: Use local models only for repetitive mechanical work
• ⚙️ Operations
  • OPS-01: Set explicit concurrency limits for agents and subagents
  • OPS-02: Make the workspace folder the source of truth and put it under git
  • OPS-03: Learn the slash commands that actually save bad sessions
  • OPS-04: Delete the old session on /new so resets do not leave junk behind
  • OPS-05: Add optional plugin tools with tools.alsoAllow
• ⏱️ Automation
  • AUTO-01: Standing orders define what, cron defines when
  • AUTO-02: Use isolated cron jobs for noisy chores
  • AUTO-03: Back up your workspace continuously, not just once
• 🏗️ Architecture
  • ARCH-01: Stop using one generic agent for everything
  • ARCH-02: Keep your orchestrator as a manager, not the doer
  • ARCH-03: Give different models different prompt files
  • ARCH-04: Predefine subagent workspaces or they lose shared context

💬 Messages

MES-01: Enable ack reactions by setting messages.ackReactionScope

Review my OpenClaw config and enable ack reactions by setting `messages.ackReactionScope` explicitly.

Do all of the following:

1. Find my OpenClaw config file.
2. Check whether `messages.ackReactionScope` is already set.
3. If it is missing, explain the available values:
   - `group-mentions`
   - `group-all`
   - `direct`
   - `all`
   - `off`
   - `none`
4. Unless I want a narrower behavior, recommend `messages.ackReactionScope = "all"`.
5. After I choose, update the config carefully.

Then show me:
- which config file you changed
- the exact `messages` block before and after
- what `messages.ackReactionScope` is set to now
- what the selected scope means
- any assumptions you made

📨 Telegram

TEL-01: Use Telegram inline buttons for recurring actions

Review my OpenClaw Telegram setup and enable inline buttons for recurring actions where taps are better than typed replies.

Do all of the following:

1. Find the active OpenClaw config file actually used by this runtime.
2. Check whether Telegram is configured and currently active.
3. Identify which Telegram account is being used for this chat/test.
4. Check whether channels.telegram.capabilities.inlineButtons is already set.
5. Unless there is a clear reason to limit scope, set: `channels.telegram.capabilities.inlineButtons = "all"`
6. Preserve any existing Telegram settings that are unrelated.
7. Do not treat plain-text option lists as buttons.
8. For real clickable Telegram buttons, send a message using an actual inline keyboard payload.
9. Use OpenClaw CLI in this form: `openclaw message send --channel telegram --account <accountId> --target <chatId> --message "<text>" --buttons '<json>'`
10. Ensure the --buttons payload is:
  - valid JSON
  - top-level array of rows
  - each row an array of button objects
  - each callback button includes text and callback_data
11. If a style field is supported by tooling, treat it only as a hint. Do not rely on Telegram per-button colors.
12. After configuration, send a real test message with clickable inline button