Codex Desktop cron automation appears to be scheduled in both local time and UTC

Environment

macOS
Codex Desktop 26.602.30954
Codex CLI 0.137.0-alpha.4
Timezone: Europe/Vienna

Automation schedule

FREQ=DAILY;BYHOUR=9;BYMINUTE=0;BYSECOND=0

Expected behavior

The automation should create one run per day at approximately 09:00 in the configured/local timezone.

Observed behavior

On 2026-06-05, the automation created a normal run at 09:01 CEST. That run completed successfully.

The same automation then created a second run at 11:01 CEST, which is 09:01 UTC. The second run was created after the first run had already completed, and the injected prompt for the second run included:

Last run: 2026-06-05T07:01:02.362Z

So the scheduler appears to have known about the successful 09:01 CEST run, but still created another run at the matching UTC wall-clock hour.

The second run did not reach model execution. It stalled during startup/tool discovery with these log lines:

startup websocket prewarm timed out
waiting for MCP server tools while building tool list server_name=adobe-docs has_cached_tool_info_snapshot=false startup_complete=false

From the timing, this looks like the RRULE is being evaluated once in local time and once in UTC, or there are two scheduler paths using different timezone assumptions.