{"version":"2.1.117","anchor":"one-time-scheduled-remote-agent-execution","canonical_anchor":"one-time-scheduled-remote-agent-execution","heading":"One-Time Scheduled Remote Agent Execution","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.117\/e\/one-time-scheduled-remote-agent-execution","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.117","markdown":"### One-Time Scheduled Remote Agent Execution\n\n**What**\n\nThe `\/schedule` command (previously `\/trigger`) now supports one-time execution at a specific time in addition to recurring cron schedules.\n\n**Usage**\n\n`\/schedule (then specify run_once_at instead of cron_expression)` **Details** - 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 **Evidence** Schedule system prompt changes (search for `\"run_once_at\"`) and description update: `\"or once at a specific time.\"` \u2014 `$J7` at line ~428477"}