Routine creation now always offers run_once_at as an alternative to a cron expression.
What's wrong with this entry?
The routine-creation instructions now always list run_once_at as an alternative to a cron expression, exactly one of which is required. Claude therefore always knows a routine can fire a single time at a future UTC timestamp and then disable itself.
RFC3339 UTC timestamp. Must be in the future. Fires once, then auto-disables.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task