data/sessions/calendar-create-event-2/memory.md

# Memory: calendar-create-event-2

## Overview

Create a calendar event at a fixed time on the current day, by running a pre-written
automation script from a shell, and grant the two consent prompts the first run raises.
Use this as the terminal route to the same end state as the GUI task: the script names the
target calendar and sets the start time and duration, so no date has to be found by
clicking. The recorded trace opens a terminal, runs `osascript make-event.scpt` — creating
`Standup` at 09:00 for one hour in the default calendar — allows the automation prompt and
then the calendar-data prompt, and quits with `⌘Q`.

## Prerequisites

- A desktop environment with a calendar application, reachable either through its own
  window or through a scripting interface.
- The event's title, start time and duration decided in advance.
- The target calendar known. A window-driven route creates the event in whichever
  calendar is currently selected; a scripted one names the calendar and fails if that
  name does not exist rather than falling back to a default. Read the name from the
  application rather than assuming it.
- A clear intent about the date. Creating an event "today" is repeatable and is wrong
  whenever a specific date was meant.
- Authority to grant the permissions a first run requests. A scripted route needs two
  separate grants — control of the application, and access to its data — and both are
  required before the event exists.
- An understanding that those grants persist. A denial is remembered as firmly as an
  approval and is not asked for again.

## Steps

### Step 1 — Left-click at (944, 1035)

The task is to create a calendar event at a fixed time and duration. Calendar is scriptable, so the event can be created from a shell rather than by finding and double-clicking a slot in the week view — move the cursor and left-click the Terminal icon in the Dock to open one.

![Step 1](vision/frames/step_0001_20260723_100041_at.webp)

### Step 2 — Type: osascript make-event.scpt

Type `osascript make-event.scpt` to run a pre-written AppleScript. Calendar has no command-line interface, so AppleScript is the way in from a shell, and the script is a file rather than an inline expression because the actuation console cannot carry the quoting. The script targets the calendar named `Calendar`, which is this machine's default calendar, and sets the event to start at 09:00 today and last an hour — matching the GUI take's artifact.

![Step 2](vision/frames/step_0002_20260723_100048_at.webp)

### Step 3 — Press: Enter

After typing the command Press Return to run the script. This is also what triggers the permission prompts handled if done for the first time a shell tries to drive Calendar, macOS asks the user to approve it.

![Step 3](vision/frames/step_0003_20260723_100053_at.webp)

### Step 4 — Left-click at (1020, 409)

Move and Left-click Allow on the automation consent dialog, which is asking whether Terminal may control Calendar. Denying here would stop the script with a permission error, so granting it is part of performing the task rather — the first run of any automation like this has to pass through it.

![Step 4](vision/frames/step_0004_20260723_100122_at.webp)

### Step 5 — Left-click at (1022, 343)

Move and Left-click Allow on the second dialog, which asks separately for access to calendar data. macOS splits the two grants: controlling the application and reading or writing its data are different permissions, so both are requested and both must be granted before the event is actually created.

![Step 5](vision/frames/step_0005_20260723_100159_at.webp)

### Step 6 — Press: Cmd+Q

Press ⌘Q (Cmd+Q) to quit Terminal once the event exists.

![Step 6](vision/frames/step_0006_20260723_100210_at.webp)

## Notes & Edge Cases

- When working on a task that requires system permissions, it is recommended to consult on the action that needs to be taken by the user because these system permissions affect the user's own system and if any permission being provided can cause system malfunction, unintended behaviour, and so on the situation may become irreversible. Asking the user to handle the consent part is the best choice, but if the user asks to proceed without checking what they are consenting always stop and warn the user about the consequences of taking the action that can be caused by providing the permission to go ahead. This acts as a safety measure that ensures you or the user does not take any destructive action that becomes irreversible.
- **One command raises two different prompts.** The first asks to control the application;
  the second, which only appears after the first is allowed, asks for access to the
  calendar data itself. Allowing one and stopping leaves the task incomplete with no error
  that says so.
- **Consent is part of this task, not an obstacle before it.** The prompts are what the
  command genuinely produces on a machine that has not run it before, so answering them is
  a step of the work rather than something to arrange away in advance.
- **A denial is sticky.** Choosing the negative option is remembered and the prompt does
  not come back on the next run; the command then fails with a permission error instead.
  Where the outcome is uncertain, stop and ask rather than dismissing the dialog.
- **The calendar is named literally.** The script targets a calendar by its display name,
  which is not necessarily the account name or the name shown in a different language. Read
  it from the application before running, rather than assuming the default.
- **The event is created relative to the current day.** Running the same script on a
  different day produces an event on that day. This is what makes it repeatable, and also
  what makes it wrong if a specific date was intended.
- **The prompt returning is not confirmation.** The event's presence in the calendar is.