Skip to content

Scheduled send ​

Labs

Scheduled send is behind the chat.scheduled_send flag and off by default. Turn it on in Settings > Labs (see Feature Flags). It is free on every plan.

Scheduled send puts a message into an agent chat or a terminal session later. The node that runs the chat or terminal stores the message and sends it, so it goes out with the app closed or the phone asleep.

Schedule a message ​

  • In Chats: click the calendar-clock button next to Send, pick Schedule send from the send options menu while a reply is running, or press Ctrl+Shift+Enter in the composer. The draft moves into the dialog. Attached files cannot be scheduled yet.
  • In the agent terminal view of a chat: open the actions (three dots) menu next to Send and choose Schedule send....
  • In a terminal: right-click the terminal (long-press on touch) and choose Schedule send....
  • From the F1 palette: run Schedule message (chats and terminals).

Triggers ​

TriggerWhat it does
At a date and timePresets In 15 min, In 1 hour and Tomorrow 9:00, or pick any date and time.
After a countdown5, 15, 30 or 60 minutes, or a custom number of minutes.
When the usage limit resetsSends about a minute after the 5 hour or weekly window resets, using the reset time the chat usage strip already shows. For a terminal the reading comes from chats on the same node and OS account, and the option is disabled when none is known.
When a chat or terminal agent finishesSends right away if that one is already idle.
When a terminal exitsSends when the terminal's process ends.

The event triggers can add Then wait N minutes before sending.

How it is sent ​

  • A chat always waits for its running turn to finish before the scheduled message goes in.
  • A terminal message presses Enter after the text (a toggle) and by default waits until the terminal's agent is idle (a toggle). Multi-line text goes into the terminal as one bracketed paste.

Pending messages ​

Pending messages show as chips above the chat composer, or floating at the top left of a terminal, with a countdown or "after X finishes". Each chip has Send now, Edit and Cancel.

A message that fails, is missed or expires stays visible with its reason, and offers Retry or Dismiss. If the node was offline at the fire time and gets to the message more than 1 hour late, it is marked Missed instead of sending a stale prompt.

Continue when the limit resets ​

When a reply fails because it hit the usage limit, the failure card offers Continue when the limit resets. It schedules the message "continue" for the reset.

Limits ​

  • Up to 20 scheduled messages per chat or terminal, 32 KB of text each.
  • Software factory chats and the Clusto Assistant do not take scheduled messages.

Clusto - remote AI coding agents over WebSocket.