Your agents show up: whether you’re there or not.
Describe the task once. Drop it on the calendar. The agent fires every morning, every week, or at the exact moment you need it: silently, in the background, with a full transcript waiting when you check in.
A calendar built for AI employees.
Every schedule targets a single agent task. Write the instruction once. The agent handles it on time, every time.
One-time
Recurring
Pick a pattern, see it on the month.
Toggle Repeat on in the ScheduleSheet to expand the recurrence block. Every combination is expressed in plain language. No cron syntax, no documentation to look up. Select a pattern to preview it:
Frequencies
Frequencies
Stop rules
Stop rules
- Never: continues indefinitely until you edit or delete the schedule.
- On date: stops after a specific calendar date.
- After N occurrences: stops automatically after a set number of firings.
Live preview
Live preview
Editing a recurring series
Editing a recurring series
- This occurrence: change only the single instance you clicked.
- This and following: change from this occurrence forward, leaving past ones intact.
- All occurrences: change the entire series, including future occurrences.
While you slept.
Agents on a schedule don’t wait for you to show up. By the time you open the app, the morning digest is already posted, the pipeline report is in your feed, and anything unusual has been flagged, all logged with full transcripts.
Open any run to see the full transcript. The conversation below shows what checking in after the fact looks like.
Illustrative scenario. Each run above maps to a recurring schedule on the Calendar page set to post into a conversation. The “spend anomaly” is the kind of narrow, scoped task scheduled runs handle best.
A week on schedule.
Recurring jobs are small individually. Across a full week they add up. The receipt below reflects the schedules on this page running as described.
The Calendar page.
Open the Calendar from the left navigation bar. The calendar itself fills the page, and a Next up panel sits on the right listing what runs soonest. The toolbar across the top carries everything else: the Month / Week / Day switcher, Today, previous and next, Filter by agent, Refresh, Hide panel, and + New schedule.
Three sections, zero guessing.
The ScheduleSheet walks you through three sections in order. Select a section to explore its fields:
The schedule type is always Agent task. The Goal field is the only required text, so be specific and keep it scoped to something the agent can finish in one run.
The PreviewPanel on the right of the sheet shows the next occurrences in real time: date, day of week, and time for each upcoming run.
The section is headed When this run finishes, and those two are the choices. Whichever you pick, the run itself is always recorded.
Open the ScheduleSheet
What to run
When to run
When this run finishes
Create schedule
Timezone handling.
Every schedule stores a timezone as an IANA string. The app defaults to your system timezone, but for agents expected to fire during business hours in a different region, you choose the zone explicitly.
Actionist computes firing times from the timezone you select rather than from your browser’s current offset, which is why the cross-zone warning card can tell you the local equivalent before you save.
Conflict detection.
The ScheduleSheet checks for overlaps against the same agent’s existing schedules in real time, before you save.
Where the result lands.
The When this run finishes section of the ScheduleSheet decides whether the run announces itself. There are two choices.
- Just run it
- Post into a conversation
One agent’s schedules, in one place.
The Calendar shows every agent at once. To see just one, open Agents, select the agent, and click the Schedule tab. The panel inside is headed Scheduled runs and lists that agent’s schedules with their next run time.
Run history.
Every execution is recorded. Run rows live in Agent Studio → Runs, not on the Calendar page: open Agents, select the agent, and click Runs. Each row carries a timestamp, a status, the source that started it, and a link through to the result.This works in the web app. Historical runs are visible there, not locked to a desktop install.
Status types
Completed
The agent task finished without error.
Failed
The task encountered an error. Open the run to see where it broke.
Timeout
The task ran too long and was ended before it finished.
Cancelled
The run was cancelled before it completed.
Running
The task is currently executing in the background.
Each row links through to the result Actionist recorded during that run: the tool calls, the model output, and the steps the agent took. That is what makes it straightforward to verify what actually happened, or to work out why something failed.
Rows also record their source, so you can tell a scheduled firing apart from a run you started by hand.
From clock to result in four steps.
Limits and defaults.
What the scheduling controls actually offer you when you sit down to create one.
Schedule states and failed runs.
A schedule that exists is not the same as a schedule that ran. These are the states worth being able to tell apart.
Check the schedule before you blame the agent
Check the schedule before you blame the agent
Timezone surprises
Timezone surprises
Make schedules reliable.
These patterns separate agents that run smoothly every day from ones that silently miss, timeout, or pile up.
Set duration accurately
Set duration accurately
Verify the timezone before saving cross-zone schedules
Verify the timezone before saving cross-zone schedules
Scheduled nothing? Check the schedule, not the agent
Scheduled nothing? Check the schedule, not the agent
Let the conflict check do its job
Let the conflict check do its job
Write narrow task instructions
Write narrow task instructions
Cloud placement is automatic
Cloud placement is automatic
Put your agents on the clock.
Open the Calendar page, describe a task, and set it to fire every morning. The agent handles it. You check the transcript when you want.
Every execution is logged with a full transcript.
Conflict detection · Timezone-aware · Every run recorded.