Calendar Quick Add (part 2)
Part 2 of the Calendar Quick Add page: why the parser is regex-first with the AI as a rare fallback, why the preview shows more than one row only when the input is genuinely ambiguous, and the repo-aware code map underneath the tab.
On this page
What it is
This is part 2 of the Calendar Quick Add page. It covers why the tab behaves the way it does, decision by decision, and then the code map underneath it: the parser, the time-zone conversion, the calendar picker, the fallback AI call, the IPC channels and the daily cost cap.
Where to find it
There is nothing new to open here. Every decision below is about the same one surface: the Calendar tab of the Quick Launch composer, opened with Ctrl+Space and described step by step on the parent page. The daily fallback cap and the saved default calendar are the only two pieces of state it keeps.
How it behaves
Design decisions worth knowing
Text-first, with a Repeat checkbox as a fallback (2026-05-24 pivot; checkbox added 2026-07-06) — the original UI had a separate free-text Repeat field, but the inline recurrence detector already handles "every weekday" / "yearly" / "every other Tuesday" from the same line. Two free-text fields where one sufficed produced inconsistent results (an Item and a Repeat that disagreed) and was more UI to read, so the free-text Repeat field was dropped — the typed line is the source of truth for the title and the RRULE. What came back later is different in kind: a small structured Repeat checkbox + frequency picker (not a second text box) that stays out of the way until you need to force a repeat the text didn't imply. It mirrors any parsed recurrence, so it can never silently disagree with the preview (see #11).
Regex first, LLM only on miss — and the AI is meant to be rare (~<1%) — after the Phase 2 layer extensions (date-anywhere scan covering "tomorrow 10am birthday", "10am tomorrow gym", "meeting at 3 today", plus slang anchors like tonite/tmrw/2morrow), the anchored regex handles the overwhelming majority of inputs with $0 spend. Haiku is the fallback for the long-tail prose the regex misses. The "AI is thinking…" pill exists so when you do hit that ~1% case you understand why the parse took an extra second — not because the feature is slow, but because your phrasing was unusual.
Multi-row preview only when the input is genuinely ambiguous (2026-05-25 tightening) — "Friday" is ambiguous (is it the whole day or a morning thing?) so Omniscio surfaces an all-day row and a 9 AM timed alternative. But "Birthday tomorrow at 2pm" is not ambiguous — the user typed the exact time — so the parser emits a single row instead of the pre-2026-05-25 trio that also showed an all-day alternative on the same date and a 30-minute look-alike that rendered identically to the 1-hour default. The dedupe layer applies to the LLM fallback path too so the same look-alike collapse holds when Haiku produces the rows.
Fixed window; tall previews scroll (changed 2026-08-01) — the Control Space window is one fixed 720×660 size for every tab; the old grow-to-fit resize was deleted because any live window grow exposed a strip the compositor cleared white for a frame (the recurring flash bug — entrance-animation contract I21). A preview taller than the window scrolls, and the Cancel/Create footer is pinned OUTSIDE the scroll region (a
flex-shrink-0sibling), so it is structurally impossible for the window edge to clip it — content scrolls, the buttons stay put (contract I34; the 2026-07-07 fix for a stale height mirror that under-sized the window). With the 2026-05-25 dedupe + exact-time-no-all-day tightening, most previews fit without scrolling anyway.Pinned by default, with a startup migration — Calendar Quick Add is high-frequency for users with Google connected, so the new tab needs to be visible without manual pinning. The one-shot migration backfills existing installs once; the sentinel
calendarQuickAddBackfilledAtprevents it from re-running every launch.Main-window toast, not an in-window pane (changed 2026-06-23) — a successful create closes the overlay immediately and confirms with a small bottom-left toast in the main Omniscio window (Open + Undo), instead of the old in-window pane that lingered for 4 seconds. Because the overlay is a separate window, the toast is relayed to the main window (
QUICK_LAUNCH_CALENDAR_NOTIFY_SUCCESS→CALENDAR_QUICK_ADD_CONFIRMED) — a renderer can't fire a toast in another window. Undo is one click (with a "Removed" confirmation); no re-prompt.Calendar picker (2026-07-01) — the tab now offers a calendar chooser and remembers your pick as the default (
calendarQuickAddDefaultCalendarId). Two deliberate constraints keep it from being clutter: it renders only when you have 2+ writable calendars (a single-calendar account never sees it), and it filters to calendars you can actually write to (via each calendar'saccessRolefrom the Google API) so a create never silently fails on a read-only feed. Primary stays the default until you choose otherwise. This supersedes the original "primary only, use the Calendar AI chat instead" stance."…of the month" without "every" offers repeating-vs-once, not whole-day-vs-morning (2026-06-02) — "Team meeting first Monday of the month" genuinely could mean a recurring monthly meeting or a single upcoming event, so Omniscio surfaces both rather than guessing. The two rows land on the real next occurrence of the pattern (computed by
firstMonthlyOccurrence), never onnowand never on a bare "next Monday" — an earlier draft mis-read the bare phrase as a one-shot on the next plain weekday with no recurrence at all. For these anchored-date phrases the all-day/9 AM alternative is dropped: the row budget is better spent on the recurring-vs-once decision, and a specific calendar anchor makes the morning-slot guess noise. Adding "every" removes the ambiguity and collapses to a single recurring row.A high-precision date scanner runs first, so a date can sit anywhere and never leaks into the title (2026-06-14) — the original parser could only spot a date at the very end of what you typed; anything after it (a time, an event name) made the date invisible, so the parser silently fell back to today and dumped the date text into the title. A dedicated scanner now finds an explicit date (numeric, ISO, month-name, bare day-of-month, weekday+day) wherever it sits and runs before the older suffix walk — so "6/21 12pm vr event" books June 21 with the clean title "Vr event" instead of "today" with "6/21 vr event" stuck in the title. It is deliberately precise over greedy: a lone number is never a date (no accidental events from "invoice 4521" or "room 1530"), and a bare dash/dot needs a year ("sprint 2-3" isn't a date). Two product calls shaped it — "next Sunday" skips to next week's Sunday (the consistent rule for every "next <weekday>"), and when a weekday and a day-of-month disagree ("Mon the 21st" when the 21st is a Sunday) Omniscio shows both dates rather than guessing. The whole change lives in the calendar layer; the shared snooze engine that powers session-snooze and alarms is untouched.
Typed time zones are honored, not dropped (2026-07-01) — the parser used to strip a zone token (EST) and book the event in your computer's zone, silently ignoring what you wrote — wrong for anyone not already in that zone. Now the zone is captured and the event is created at that wall-clock in that IANA zone and tagged with it, so "9am EST" is 09:00
America/New_Yorkregardless of the host. The conversion goes through a small DST-correct shared helper (wall-clock-zone.ts) that recomputes the instant with the target zone's real offset for that date, and it emits an offset-bearing ISO so the strict create-event schema (which requires an offset) is untouched. Coverage is abbreviation→IANA for the common US zones + UTC/GMT; anything unrecognized still falls through to the AI parser, and no-zone input is byte-identical to the old host-zone behavior. Reported via in-app feedback (a Pacific-time user whose "EST" events landed at the wrong hour).A dangling "every" is understood, and a Repeat box is the fallback (2026-07-06) — typing the day first and the repeat last ("Kathleen Tuesday 10am every") used to leave the bare word "every" stranded in the title with no recurrence, because the parser only recognized a complete phrase like "every Tuesday". Now, when a leftover "every" / "every other" has a weekday to anchor it, the parser reads it as every [other] <that weekday> — built from the day the event actually lands on — and produces a single weekly / biweekly row; with no weekday it just cleans the stray word out of the title. This only kicks in after the normal recurrence match misses, so nothing that already parsed changes (verified against the full ~1,500-phrase test set with zero regressions). For everything the text still can't express — an exact date you want to repeat, an unusual phrasing — a small Repeat checkbox + frequency picker below the preview lets you force it. The box is renderer-only (it reuses the same recurrence builder the parser uses) and defaults to mirroring any recurrence the text already implied, so it never disagrees with the preview. Reported via a screenshot of "Kathleen Tuesday 10:00 AM every" previewing as the title "Kathleen every".
Related
The user-facing walkthrough of the tab is on the parent page. The composer it lives in is the Quick Launch modal, the connection that gates it is on the Google Integrations page, and the alarm tab that shares the same natural-language, regex-first, Haiku-fallback shape is on the Alarms page. The date and time grammar is the same engine as the one on the Snooze a session page.
Last verified 2026-10-06