Schedules
A schedule is an instruction an agent carries out at a set time, whether or not you have Endue open. A recurring schedule runs again and again. A one-time schedule runs once.
When to use it
When the same request comes round again: a morning inbox digest, a Monday report, an overnight check for something that should not have changed. If you have asked an agent the same thing three times, it is a recurring schedule.
When you want something done once, later: a reminder in 30 minutes, another look at something tomorrow morning. That is a one-time schedule.
Create a recurring schedule
The simplest way is to ask. In a conversation with the agent, say what should happen and when — “do this every weekday at 8am” — and it creates the schedule, which you can then review.
-
Get the task right first. Run it once by hand. A schedule repeats whatever you asked for, including the ambiguity.
-
Set the cadence. A recurring schedule repeats with a timezone — every weekday at 08:00 in Asia/Seoul, the first of the month, every four hours.
-
Say where the result goes. Usually an output, which you will find waiting with a notification pointing at it.
-
Watch the first few runs. The gap between what you meant and what the agent does shows up immediately, and is cheapest to fix then.
One-time schedules
Ask in a conversation: “remind me in 30 minutes”, or “check this once tomorrow at 9am”. The agent schedules it to run once and replies with the exact time, in your time zone.
When that time comes, the agent carries out the instruction in the same conversation. A Scheduled run · (name) line marks where it starts, the agent’s reply follows it, and you get a notification. If a reply is still being written in that conversation at that moment, the schedule waits for it to finish instead of skipping.
A one-time schedule that has run stays in the list as Done, so the conversation with its result is still one click away.
Until it runs, you can cancel it, or ask the agent to move it to another time. A one-time schedule cannot be paused.
Schedules the agent set itself
An agent can also schedule a follow-up on its own, for example to check again on something that has not finished yet. These schedules are marked Set by agent and link to the conversation where the agent set them, so you can see why each one exists. If you do not need one, cancel it.
The agent works within limits here:
- It can hold at most five active schedules it set itself.
- It can only make one-time schedules by itself. When it thinks something should repeat, it proposes a recurring schedule to you instead of creating one.
- A chain of follow-ups, where a scheduled run sets the next one, stops after three steps.
What happens on each run
The schedule fires, the agent runs the instruction as though you had sent it, and the result lands in your workspace. By default you get a notification when it finishes, and another if it fails — see Notifications.
A recurring schedule that keeps failing is paused, and you are told. That is deliberate: a broken schedule that retries every hour for a week is worse than one that stops and says so.
Hear only when something changes
Some recurring schedules are watches: a check of a pricing page every hour, or a wait for a reply from one person. Most of their runs find nothing new, and a notification after each one is noise.
For a watch, set the schedule’s Notifications to Only when the agent notifies. On each run the agent then decides whether you need to know what it found:
- Something changed. The agent sends you one line of up to 200 characters, such as “Acme Pro dropped from $29 to $25 a month”. That line is the notification. It appears in the app and in the desktop app, and arrives as a browser or phone push if you have turned those on.
- Nothing changed. The run ends quietly. Its answer stays in the schedule’s conversation, and the run stays in the schedule’s history.
Failed and skipped runs are reported either way.
You can ask for this in a conversation. “Check the pricing page every hour and tell me if it changes” gets you a recurring schedule that is already set this way. To switch an existing schedule, use the Notifications selector on its page, at any time. The create-schedule dialog has the same choice, with Every run as the default.
Nobody is there to approve
This is the most important thing to understand about scheduled work, and it applies to one-time schedules too.
An unattended run cannot ask you anything. An action that would normally stop for approval — sending an email, posting to a channel, deleting something — is refused, not queued.
Design around it:
| Instead of | Ask for |
|---|---|
| “Email me the summary” | “Write the summary as an output” — the notification brings you to it |
| “Post the digest to Slack” | An output you post yourself once you have read it |
| “Reply to anything urgent” | “Draft replies to anything urgent” — drafting is not gated |
The same applies to questions: a schedule that needs a decision has nobody to ask, so make the instruction specific enough not to need one.
Managing schedules
Schedules are listed per agent, and each has its own page with its timing, its history, and the runs it produced. You can pause, edit, or cancel a recurring schedule at any time, and cancel a one-time schedule until it runs. Agents can list and manage their own schedules when you ask them to.
Limits
- An unattended run refuses gated actions. There is no “approve in advance”.
- A schedule belongs to one agent and carries one instruction.
- Repeated failures pause a recurring schedule rather than retrying indefinitely.
- You set up a one-time schedule by asking in a conversation. It can be from 1 minute to 30 days ahead.
- If you ask for a one-time schedule from a channel such as Slack, the result does not go back to the channel. It appears in the conversation in Endue and as a notification.
- An agent can hold at most five active schedules it set itself, and a chain of follow-ups stops after three steps.
- Schedules run on Endue’s servers, so they cannot reach anything on your own machine.
- In a schedule set to Only when the agent notifies, the agent decides what counts as a change. It can miss one, or tell you about one that does not matter. The schedule’s history shows what each run saw.
- An agent sends at most one notice per run and 20 per day, with the day starting at midnight Korea time (KST). When it reaches 20 you get one notice saying so, and the rest of that day’s notices are not sent.