// Parse natural-language schedule requests into Apple Calendar events, especially Chinese phrases such as "明早 8 点开会" or multiple events in one sentence. Use when Codex needs to extract event details, check Apple Calendar conflicts before writing, warn about overlaps, and create events with a default 30-minute reminder on macOS.
| name | apple-calendar-scheduler |
| description | Parse natural-language schedule requests into Apple Calendar events, especially Chinese phrases such as "明早 8 点开会" or multiple events in one sentence. Use when Codex needs to extract event details, check Apple Calendar conflicts before writing, warn about overlaps, and create events with a default 30-minute reminder on macOS. |
Convert natural-language schedule requests into structured events, check Apple Calendar for overlaps, and create events only after the event data is complete enough to write safely.
Follow this sequence every time:
alert_minutes_before with 30 when the user did not specify a reminder.List existing events in a window:
python3 scripts/list_events.py --start 2026-03-24T00:00:00+08:00 --end 2026-03-25T00:00:00+08:00
Check one or more candidate events for conflicts:
python3 scripts/detect_conflicts.py --input-file /tmp/events.json
Create events after conflict checks pass:
python3 scripts/create_event.py --input-file /tmp/events.json
Parse Chinese schedule text into structured events and unresolved questions:
python3 scripts/parse_schedule.py --text "明早1个小时买菜，9:30之后不行，然后晚上6点朋友到家里聚餐4小时"
Suggest concrete slots for unresolved items:
python3 scripts/suggest_slots.py --input-file /tmp/parsed.json
Run the full workflow in one shot:
python3 scripts/schedule_from_text.py --text "明早1个小时买菜，9:30之后不行，然后晚上6点朋友到家里聚餐4小时"
Map user language into concise event titles:
title: 买菜title: 朋友聚餐, location: 家里Infer an end time only when duration is explicit or strongly implied:
09:30Convert constraints like "9:30 之后不行" into a scheduling constraint: infer the latest possible start time and schedule accordingly. Do not ask for confirmation.
Use the parser output conservatively:
events is non-empty and unresolved is empty, move on to conflict detection.constraints are present without an exact start, treat them as availability hints, not a scheduled event.Python scripts require Python 3.10+ due to type union syntax. On macOS with Python 3.9, use JXA directly via osascript -l JavaScript.
IMPORTANT: Use cal.events.push(newEvent) — do NOT use new app.Event({..., calendar: cal}) as it silently fails.
osascript -l JavaScript <<'JXA'
const app = Application("Calendar");
app.includeStandardAdditions = true;
const cal = app.calendars.byName("个人");
const s1 = new Date("2026-03-24T08:30:00+08:00");
const e1 = new Date("2026-03-24T09:30:00+08:00");
const ev1 = new app.Event({summary: "买菜", startDate: s1, endDate: e1});
cal.events.push(ev1);
const s2 = new Date("2026-03-24T18:00:00+08:00");
const e2 = new Date("2026-03-24T20:00:00+08:00");
const ev2 = new app.Event({summary: "朋友聚餐", startDate: s2, endDate: e2});
cal.events.push(ev2);
JSON.stringify({ok: true, created: 2});
JXA
osascript -l JavaScript <<'JXA'
const app = Application("Calendar");
const cal = app.calendars.byName("个人");
const events = cal.events();
events.filter(e => e.summary() === "买菜").forEach(e => e.delete());
JSON.stringify({ok: true});
JXA
new Date("2026-03-24T08:30:00+08:00") works correctly in JXA; toISOString() shows UTC but Calendar displays in local time.list_events.py after creation.TypeError: unsupported operand type(s) for |, fall back to JXA directly.