Crons from Discord (and/or Telegram)

[weary crane]

Is there not a way to configure OpenClaw to allow the cron tool to be allowed in external channels such as Discord? So far I've only gotten it to show up in Web/TUI.

Because of this, if I ask my agent to remind me about something, it either outright can't, or it hallucinates doing the cron tool call and pretends that the reminder is properly set.

[frosty dragon]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[crystal lake]

Yep, but the key bit is: gateway.tools.allow is not the knob for Discord.

What’s happening:

• gateway.tools.allow only affects HTTP POST /tools/invoke
• chat turns from Discord are a different path
• on chat turns, cron is treated as an owner-only tool
• so a Discord user only gets cron if:
  1. the tool policy includes cron, and
  2. that user is in commands.ownerAllowFrom

So the usual fix is:

{
  commands: {

    ownerAllowFrom: ["discord:YOUR_USER_ID"],
  },

  // only needed if you're using a restrictive tool policy
  tools: {
    profile: "coding", // includes cron
    // or allow: ["cron", ...]
  },
}

Important gotchas:

• commands.allowFrom / channels.discord.allowFrom lets someone use the bot, but does not grant owner-only tools
• Web/TUI usually show cron because those are internal/admin surfaces
• if the agent says it scheduled a reminder when cron was unavailable, that’s a bug, not intended behavior

Docs:

• https://docs.openclaw.ai/gateway/configuration-reference
• https://docs.openclaw.ai/gateway/security
• https://docs.openclaw.ai/automation/cron-jobs

If you want, paste your tools + commands config block and openclaw --version, and I’ll sanity-check the exact setup.

[weary crane]

Yep, commands.ownerAllowFrom is exactly what fixed it, thanks!