Schedules and background work
An agent normally answers when you write. It can also run schedules, delegate tasks to background workers, and send you direct messages.
Schedules
Section titled “Schedules”A schedule wakes an agent at a set time with a prompt it wrote for itself, and the agent posts its answer in the channel where the schedule was made. Ask for one in that channel:
Every weekday at 9:00, post a short summary of what changed in the notes channel.Remind me in 45 minutes to send the invoice.On Mondays and Thursdays at 17:30, ask me what I got done.The schedule tools
Section titled “The schedule tools”| Tool | What it does |
|---|---|
schedule_create |
Makes a schedule from a title, a prompt, and one kind of timing, and optionally a precheck and a time_limit_minutes. |
schedule_list |
Lists the channel’s schedules with their next run and the prechecks the host offers, or one schedule in full with id. An agent sees its own schedules from all its conversations, each with where it fires, and can read another agent’s schedules with agent. |
schedule_update |
Changes the title, the prompt, the timing, the precheck, or the time limit of one schedule (precheck: null and time_limit_minutes: null remove them). A run may use it to keep its own prompt current. |
schedule_cancel |
Deletes one schedule; an agent may cancel any of its own, in any conversation. |
Owners and admins can create, change, and cancel schedules. Any speaker can list them. An agent can change only its own schedules, whichever of its conversations (Discord or the web app) made them; to change another’s, ask that agent.
The timing is one of these:
| Fields | Runs |
|---|---|
in_minutes |
Once, that many minutes from now. |
at |
Once, at YYYY-MM-DD HH:MM. |
time |
Every day at HH:MM. Add every_days (1 to 365) for every few days, counted from start_date, or weekdays for chosen days. |
Limits
Section titled “Limits”- A channel holds up to 20 schedules, and a prompt is up to 8,000 characters.
- The first run must be within 366 days. A time that has already passed is refused.
- The scheduler checks for due schedules every 30 seconds.
- The scheduler skips a run it finds more than 12 hours late, for example after the bot was down.
- A schedule runs with the tier of the person who made it, so someone of a lower tier cannot rewrite it.
- Archiving an agent cancels its schedules.
Time limit and quiet runs
Section titled “Time limit and quiet runs”A scheduled run is stopped after 10 minutes of work, as any turn is, because nobody is in the conversation to be asked for more time.
Give a schedule that works longer its own limit with time_limit_minutes, from 1 to 240 (four hours); it applies to every run of that schedule and never passes the host’s long-running cap.
Turning on long-running for the agent’s room does the same for all its turns.
A run that is stopped at its limit posts a notice in the channel that says where it stopped and how to allow more time.
A run that has nothing to report may answer with nothing: the channel gets no message and the run counts as done. A prompt such as “send nothing if there is no progress” therefore works as written.
Prechecks
Section titled “Prechecks”A precheck is a cheap check the host runs before a schedule’s turn, so a daily check whose answer is “all normal” on most days costs no model turn on those days.
The host’s plugins register prechecks by name; schedule_list shows them with their descriptions, and an agent attaches one with precheck.
- When the precheck finds nothing, the turn does not run. It may post a short note in the channel instead, in small text.
- When it finds something, the turn runs with what it found added after the prompt.
- When it fails or takes too long (60 seconds unless it sets its own limit), the turn runs anyway with the error, so the agent can look into it.
The last run in schedule_list and /roundtable schedule list shows which of these happened, such as skipped by precheck (HRV 52 ms, as usual.).
Attaching a precheck follows the same tier rules as changing the schedule.
When the host runs pi-roundtable-sandbox’s precheck runner, an agent can also write a schedule’s precheck itself with precheck_script: a short JavaScript module that reads what it needs through the MCP tools the host grants for that schedule and returns whether to wake.
It runs in a sealed container with no network and no host files, never in the bot’s own process.
schedule_list explains how to write one and what it may call; without the runner, the tools do not offer scripts.
A script’s tool calls follow the same holds as the agent’s own: saving a script that calls a held tool, such as sending mail, waits for the owner’s approval once, and each run may call only the tools saved with it.
See Services and addons for registering one.
Time zone
Section titled “Time zone”Times are in the timeZone setting of roundtable.config.ts, which is UTC when you set none.
The tools tell the agent the zone and the current time, and a refusal for a past time names both.
See Configure.
See and cancel them yourself
Section titled “See and cancel them yourself”/roundtable schedule list shows every channel’s schedules.
/roundtable schedule cancel cancels one, with an autocomplete list to pick from.
Only you can use the command, and the answer is visible only to you.
Delegated work
Section titled “Delegated work”An agent can hand a long piece of research to a background worker with delegate_task, which takes a title and a self-contained task of up to 4,000 characters.
- The worker’s only tools are web search and page reading. It sees only the task.
- The agent keeps working with you. The worker’s report arrives as a new turn in that channel, and the agent answers you with it.
- Where Discord allows it, a thread opens in the channel with the task. It ends with the report, or with the error when the worker fails.
- A channel can have 3 delegated tasks running at once.
- A task that runs for 20 minutes is stopped and reported as failed.
- Running tasks are kept in memory. A restart drops them without sending a report to the channel.
The worker uses the model in the delegation setting.
Without one it uses the agents’ model, with the thinking level medium.
The bot needs Create Public Threads for the thread; see Set up the Discord bot.
Direct messages to you
Section titled “Direct messages to you”notify (notify_owner in 0.8, still accepted until 1.0) sends you a notice on the surface of the conversation it came from: from a web app room, a notice on the web app’s Home and a push to your devices; from Discord, a Discord direct message.
An agent uses it only when you ask to be notified or reminded, because its normal reply already reaches you in the conversation.
Only your own turns can use it.
Every Friday at 16:00, check the open tasks and send me the list by direct message.Where things are delivered
Section titled “Where things are delivered”Everything an agent sends goes back to the conversation the work came from, on its surface.
A schedule made in a web app room runs in that room, and its report and any notice it sends stay in the web app; one made in a Discord channel stays in Discord.
The same holds for a delegated or coding task’s thread and report, a question card, a timeout card, and a message between agents: message_agent without a conversation reaches the other agent’s room when sent from a room, and its Discord channel when sent from Discord.
Only when the conversation’s own surface cannot reach you, for example you have no web app on a host where the schedule ran in a conversation without one, does a notice go to another surface, and the host logs that it did, naming both surfaces. The web app may also push to your phone a notice that Discord delivered: that echo goes only to you, never into a conversation.