Asking for something later

Ask an agent for something in the future and it arranges it:

• •"Every Sunday send me the sales report"
• •"On the 1st of each month email me the summary"
• •"In five days chase customer 1 about their invoice"

It appears under Scheduled, and runs on its own from then on.

The agent has to be able to do it

Scheduling comes from the built-in toolkit, so an agent that has not been given it cannot arrange anything — and it will not say so. It answers the sentence in words, which reads exactly like agreement, and nothing appears under Scheduled.

Add a Built-in toolkit connection and every agent made afterwards has it. Agents that already existed do not pick it up on their own; whoever runs your installation can link them in one step.

What actually gets stored

The sentence you wrote, not a plan built from it. When the task comes due that sentence is handed back to the agent and it works out what to do with the tools it has then.

That is deliberate. A stored plan compiled against today's tools quietly stops matching them as your connections change; a sentence still means what it meant. It also means you can read your own schedule back and recognise it.

It is not a way around the rules

A scheduled run goes through the same runtime as anything you type: the same tool checks, the same policy, the same approval gate. A scheduled deletion still stops and waits for a person. Nothing gets easier because it was asked for in advance.

Where the answer goes

To wherever you asked. A task created in Telegram replies in that chat, one created in the dashboard appears in that conversation. If you delete the thread, the task keeps working and opens a new one rather than disappearing.

Changing your mind

From Scheduled you can rename a task, move it to a different day or time, pause it, or cancel it. Or just ask the agent — "what have I got scheduled?", "pause the weekly report", "move it to Mondays". It is the same list either way.

Pausing stops it running and keeps it. Cancelling is permanent, though the record of what it was and what it did stays.

When something goes wrong

A task that fails records why, and you can see it on the same page. After five consecutive failures it pauses itself — something that has failed five times is not going to succeed on the sixth, and quietly failing forever is worse than stopping and saying so.

Times run in the workspace's timezone — the one under Settings — so "every Sunday at nine" means nine where you are, including across daylight saving. A task keeps the timezone it was created in, so changing the workspace's zone later moves nothing that already exists.