What's wrong with this entry?
The /schedule command (previously /trigger) now supports one-time execution at a specific time in addition to recurring cron schedules.
/schedule (then specify run_once_at instead of cron_expression)- Use
"run_once_at": "YYYY-MM-DDTHH:MM:SSZ"(RFC 3339 UTC) instead of a cron expression - The timestamp must be in the future
- When the user specifies a local time, the agent converts it to UTC and confirms
Schedule system prompt changes (search for "run_once_at") and description update: "or once at a specific time." — $J7 at line ~428477
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.