time-based-actions

Automating scheduling and reminders involves parsing natural language time expressions and routing requests to the correct tool, such as reminder_create or schedule_create, to execute actions accurately. The system grounds relative times and disambiguates anchored expressions like "noon" for reliable execution.

Routing time-based requests requires unified decision logic that directs each user input to the appropriate tool, whether that is task_list_add for simple notes, assistant notifications for immediate alerts, or schedule_create for recurring events, enforcing correct one-shot or recurring semantics.

Relative time parsing anchors ambiguous expressions by grounding them against the current_time input, applying disambiguation rules to resolve vague time references like "in 5 minutes" or "noon" into precise, actionable timestamps for the routing engine.

You can set up both recurring schedules and one-shot reminders using a single routing guide that enforces distinct semantics for each mode, ensuring reminder_create handles single notifications while schedule_create manages repeating events with proper time grounding.

The reminder automation system supports multi-channel delivery by applying routing defaults that direct assistant notifications and scheduled alerts across appropriate channels, ensuring reliable execution whether the action is notify-only or execute-mode.

Scheduled reminders fail when time grounding rules are not properly applied to parse relative times or when the current_time input is missing, preventing the routing logic from disambiguating time expressions and dispatching to the correct tool.