Add an iCalendar feed and blanks can answer availability questions from your busy times. Event times are sent to the model; event titles and locations are not.
Busy intervals, with titles replaced by numbered tokens.
sent to the model
not sent
Each event travels as a token ([EVENT 1], [EVENT 2], …) plus its date and its start and end times, and the current moment travels with them. What never travels is what any event is.
After the answer returns, on your machine.
When an answer refers to an event, the token in the model's output is replaced with the real title locally, the same mechanism identity fields use. A question about a specific event ("where is the dentist appointment") is matched to its token on your machine when exactly one event matches those words; an ambiguous word matches nothing. The title still does not go out.
Times are sent as minutes since midnight.
you type
you get
Because the model receives numeric intervals, finding a gap is arithmetic on those numbers rather than interpretation of prose.
One command; nothing is sent until a feed exists.
opencues calendar add <url> registers an iCalendar (.ics or webcal) feed. opencues calendar list, remove, and refresh manage it. The parsed feed is written to ~/.cues/calendar.json, which every host reads. The feature is on by default but sends nothing until a feed is added, because with no feed there is no data.
Titles are not sent to a model. They are still on your machine.
Titles and locations are held locally and substituted into answers after they return. With debug-mode: on they appear in your local log file (/tmp/opencues.log), like any other data your machine handles. The claim is specifically: event titles and locations are not included in model requests.