PandaOSPandaOS
Chat with Panda

Scheduled messages

Have a chat come back to something later or repeat a check. Tell me when wakes it only when what you are waiting for happens.

Feature Updated 20 Nov 2026

Two ways to come back later

A chat can come back to work without you typing. There are two kinds:

What happensCosts a turn
Scheduled messageSends your message at a set time, once or on repeat. The agent answers each time.Every time it is sent
Tell me whenPandaOS keeps an eye on something and only brings in the agent when it happens.Only when it happens

Use a scheduled message for "in 30 minutes, ask how the data load is going". Use Tell me when for "let me know when the nightly import finishes or shows an error", because waiting costs nothing until the moment it matters.

Both work the same on every engine, keep running after PandaOS restarts, and wake a chat that is idle. They only run while PandaOS is open.

Schedule a message

Ask in the chat, for example "check the deploy every 10 minutes until it is green". Or open the + menu in the message box and choose Schedule:

  • In 30 min, Tomorrow 9:00 and Every 10 min attach that time to your draft.
  • Custom time… lets you pick a day and a time, or a repeat every so many minutes or hours. A repeat stops when the agent says the goal is reached, after a number of runs, or at a time.

A chip appears in the message box. Type the message and press send. Nothing is sent now: the message goes out at the chosen time. The chip's cross removes the schedule and keeps your text.

A repeat always ends after 12 hours at the latest. A repeat that comes due while the chat is busy skips that run. A one-time message waits until the chat is free.

Tell me when

Choose +, Schedule, Tell me when… and describe what to wait for in your own words, for example "the checks on pull request 1421 are through" or "import.log shows DONE or ERROR". Or say it in the chat.

The agent sets up a check that PandaOS runs by itself. It watches a command, a file, a web address, a read-only PandaOS app action, or another chat's state. It tries the check once and tells you in plain words what it will tell you about. A command asks for your approval once, showing the exact command.

While nothing happens, the chat stays quiet. When the condition is met, the chat wakes with a short marker such as "Watch fired: status is success" and the agent tells you what happened. If the chat is busy at that moment, it hears about it as soon as it is free. A check that finds nothing within 12 hours stops and tells you so.

See, pause, edit and stop

Everything scheduled in a chat is listed on top of the message box, next to the message queue, for example "3 scheduled · next in 4 min". Each line shows the message, how often it runs and when it runs next. Hover a line to Pause, Edit or Stop it. Click it for the details: the full message, the rule a Tell me when checks, and any error. It also says who set it: you, the agent, another chat or the Director.

Chats with something scheduled show a small clock in the sidebar. A chat in a worktree or on a machine shows that mark instead, and its tooltip still names the schedule. A chat holds up to 5 schedules at a time.

Other chats and the Director can schedule into a chat too. The Director uses this to check back on work it started.

Schedule or Automation?

A schedule belongs to a chat, because it needs what the chat already knows, like "the deploy we just started". A fixed job that needs no conversation, like "every Monday email the KPI summary", belongs in an Automation, which runs its steps without a chat.