ai-timer

Scheduling recurring reminders with natural language commands translates phrases like "every weekday at 18:00" into validated timer.md table rows. The system parses intent and fields to create correctly formatted recurring timer entries automatically.

Updating existing timer schedules without manual table editing is possible by requesting changes through chat. You can modify time, days, name, or prompt for an existing timer, and the system validates the update before applying it.

Timer.md management for heartbeat channel timers is the process of adding, updating, and deleting recurring timer definitions in a structured table. It uses a validation script to ensure schedule entries are correctly formatted before runtime execution.

Safely renaming a recurring timer and cleaning up runtime state requires updating the timer.md identity and removing old runtime references. This prevents timer duplication or misfiring when switching schedule kinds or changing timer names.

The heartbeat channel validate script supports interval-based recurrences alongside daily, weekday, and weekend time lists. It validates parsed natural language inputs to ensure interval formats like "every 2h" are correctly structured in the timer.md file.

Limitations of managing recurring timers through chat commands include dependency on the heartbeat-channel validate script for state validation. Complex schedule changes require parsing intent correctly, and renaming timers demands runtime state cleanup to avoid duplication.