Recurring todos

Some work comes back: the weekly report, the monthly invoice run, watering the plants. Instead of recreating the todo, give it a repeat rule.

Setting a rule

Open the due-date selector on a todo and expand Repeat. A rule is Daily, Weekly or Monthly, every n days, weeks or months; a weekly rule can name the weekdays it falls on, and a monthly rule is anchored to the due date’s day of the month — the 31st clamps to the 28th in February and returns to the 31st in March rather than drifting.

A rule always has a due date as its anchor. Set a rule on a todo without one and the next matching day is picked for you; Clear date & repeat removes both together. Pause keeps the rule but stops it spawning until you Resume.

What happens on completion

When a recurring todo is completed, the server creates the next occurrence: a fresh todo with the same title, description, labels, assignee and list, due on the next date the rule names, in your default open state. The original stays done, so your history is intact — each occurrence has its own identifier and timeline. A todo spawns at most one successor; reopening and completing it again does not create a second.

A recurring subtodo stops when its parent is done or canceled, since the decomposition it belonged to is finished.

Where the rule shows

The due-date chip reads as the date followed by a summary of the rule, and every change to the rule is written to the todo’s activity timeline. Agents set and clear rules through the MCP server’s save_todo.