Calendar
A per-project scheduler that runs playbooks and sends Argus messages automatically — once or on a recurrence — but only while Scape is open on a Mac you've switched Active.
Every project has a Calendar — a scheduler where you set playbook runs and messages to your Argus managers to happen automatically on a clock. Schedule something once, or on a daily, weekly, or monthly recurrence.
The Calendar is the time-based counterpart to Triggers: a trigger fires when a condition is met, a calendar event fires at a time.
Opening the Calendar
The Calendar is always present in the project sidebar, alongside Profiles and Integrations — there's no Creation Picker step to add it. Click it to open the Calendar tab in the center pane. Switch between Day, Week, and Month views from the header; your chosen view is remembered per project on that Mac.
Scheduling an event
Create an event from the Calendar view (click a day/time slot or the create button). Each event has:
| Field | What it is |
|---|---|
| Title | A label for the event. |
| Action | What runs when the event fires — a playbook or a message to an Argus. The picker only offers targets that resolve in this project: the project's playbooks and its Argus managers. |
| Message | For an Argus message, the body delivered to the manager. Scheduled playbook runs don't receive a calendar input — this field applies to Argus messages. |
| Date & time | When the first (or only) occurrence happens. |
| Recurrence | None, Daily, Weekly, or Monthly, with an interval (every N days/weeks/months) and, for weekly, which weekdays. |
| Time zone | An IANA time zone, or System. Recurrence is DST-aware — a spring-forward gap resolves to the first valid time. |
Moving and skipping occurrences
You can change a single occurrence without touching the rest of the series:
- Move — drag an occurrence, or edit its time. Choose the scope: This occurrence writes a one-off override; All moves the whole series anchor.
- Skip — skip a single occurrence (it renders as skipped). Skipping doesn't delete the event or affect any other occurrence, and you can restore a skipped occurrence later.
Turning the calendar on
A calendar is Active or Inactive per Mac, controlled by the toggle in the Calendar tab's header. This toggle is the only thing that lets events fire — turning it on pops a confirmation, because scheduled actions will start running on that machine while Scape is open.
Key consequences:
- Off by default on every device. Enabling on one Mac doesn't enable it anywhere else.
- Each Active device runs independently. If you switch the same calendar Active on two Macs, each may run the same occurrence.
- Firing only happens while Scape is open. There's no server-side scheduler — a closed app runs nothing.
What happens to missed occurrences
Firing depends on the calendar being Active and the app being awake, so occurrences can come due while nothing is running. When Scape reconciles, how it treats an occurrence depends on how late it is:
- On time (came due in the last ~5 minutes) — dispatches normally.
- Late (roughly 5–30 minutes) — dispatches once as a catch-up.
- Missed (more than ~30 minutes late) — does not auto-fire.
Two floors bound this catch-up:
- Only occurrences after you last switched the calendar Active are eligible. Turning a calendar Active sets a floor at that moment — occurrences that came due before you enabled it never catch up, even with Skip if missed off. Catch-up covers only occurrences that came due while an already-Active calendar was asleep or closed.
- Skip if missed affects only the late catch-up band. An on-time occurrence dispatches regardless of this setting; when Skip if missed is on, an occurrence that fell into the late band is not caught up.
Day summaries
The Day view has a Generate summary button that produces a one-line rollup of that day's occurrences — counts by outcome plus the next scheduled time, e.g. "3 scheduled · 1 succeeded · 1 failed · next 4 PM", or "Nothing scheduled." The summary always works; with an active subscription it can be AI-enriched, otherwise it falls back to the deterministic rollup.
MCP tools
Agents have full parity on event data — they can create, edit, move, and skip events for you — but there is deliberately no tool to enable the calendar or make it fire. Only you can switch a calendar Active.
| Tool | Description |
|---|---|
create_calendar_event | Create a scheduled event (playbook or Argus message), with optional recurrence, interval, weekdays, time zone, and skip-if-missed. |
update_calendar_event | Edit an event. Requires the expectedRevision you read — a stale revision is refused rather than clobbering a concurrent change. |
delete_calendar_event | Remove an event. |
move_calendar_event | Move an occurrence by originalOccurrenceAt, with scope this (one occurrence) or all (the series). DST-aware. |
skip_calendar_event | Skip a single occurrence (skip: true) or restore it (skip: false). |
generate_calendar_summary | The day rollup — the same summary as the Day view's button. |