Skip to content
TomoriBot

Scheduled Tasks

TomoriBot can set reminders and schedule tasks for later — one-time or recurring. The easiest way is to just ask her; she creates the task through her create_task tool. Scheduled tasks are persona-specific.

Creating One

Section titled “Creating One”

Just tell her in chat:

remind me to submit the report at 14:30
every Friday at 8pm, post a reminder that game night is starting

She parses the time and recurrence and schedules it. Reminders ping the target user when they fire; tasks are silent self-actions the persona performs at the scheduled time.

Timezones

Section titled “Timezones”

Absolute times (“at 14:30”, “on Friday at 8pm”) are interpreted in the server’s timezone (/server timezone) by default. If you’ve set a personal timezone with /personal timezone, the AI sees your local clock in context and labels your times with your UTC offset when creating the task — the bot then does the conversion deterministically, so “remind me at 9am” means your 9am even if the server is on another continent. Relative times (“in 2 hours”) are timezone-free and always safe.

When a reminder targets a user whose personal timezone differs from the server’s, the confirmation embed shows both clocks (server time and the target’s local time), so a mislabeled time is immediately visible and can be fixed with a follow-up message or /scheduled-task edit.

Managing Tasks

Section titled “Managing Tasks”

Two slash commands let you review and adjust existing schedules:

  • /scheduled-task edit — change a task’s content, next trigger time, recurrence interval, or whether it’s a reminder. Set the interval to 0 to disable recurrence.
  • /scheduled-task remove — delete a reminder or task.

Both open a picker listing your existing schedules (persona, time, channel, and recurrence), so you don’t need to remember IDs.

How Delivery Works

Section titled “How Delivery Works”

Reminders are delivered by an in-app scheduler and are only marked done after delivery succeeds — if a delivery is aborted or the channel queue is cleared, it’s automatically rescheduled and retried. For the runtime details, see the architecture overview.

Scheduling is one of several agentic capabilities — see Tools & Extensions for the full picture.