Automations use UTC instead of Europe/Warsaw for next-run time

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.61608 (build 5200)

What subscription do you have?

Pro Version

What platform is your computer?

Darwin 25.5.0 arm64 arm (macOS 26.5.2, Europe/Warsaw)

What issue are you seeing?

A weekly Codex automation is stored with an explicit Europe/Warsaw timezone:

DTSTART;TZID=Europe/Warsaw:20260713T093000
RRULE:FREQ=WEEKLY;BYDAY=MO;BYHOUR=9;BYMINUTE=30;BYSECOND=0

On Monday, July 13, 2026, at approximately 11:19 CEST, the Codex App displayed:

Mondays at 9:30 AM · Next run in 11 minutes

In July, Warsaw is UTC+2. A run in 11 minutes from 11:19 CEST means 11:30 CEST, which is 09:30 UTC. This strongly suggests that the next-run calculation is interpreting the configured 09:30 as UTC and ignoring TZID=Europe/Warsaw.

The saved recurrence itself is correct. It is not yet confirmed whether this affects only the displayed countdown or also the actual execution time.

What steps can reproduce the bug?

1. Set the macOS timezone to Europe/Warsaw.
2. Create an active weekly Codex automation for Monday at 09:30 Warsaw time.
3. Verify that the saved automation contains:

DTSTART;TZID=Europe/Warsaw:20260713T093000
RRULE:FREQ=WEEKLY;BYDAY=MO;BYHOUR=9;BYMINUTE=30;BYSECOND=0

1. On Monday after 09:30 CEST, open the Automations list.
2. At approximately 11:19 CEST, observe that the app says the next run is in 11 minutes.

The displayed time therefore corresponds to 09:30 UTC / 11:30 Warsaw rather than 09:30 Warsaw.

What is the expected behavior?

The automation should run every Monday at 09:30 in Europe/Warsaw.

At 11:19 CEST on Monday, July 13, the 09:30 local occurrence had already passed. The next run should therefore have been Monday, July 20, 2026, at 09:30 CEST (approximately 6 days and 22 hours later), not 11 minutes later.

The countdown and actual scheduler should both respect the timezone declared in DTSTART;TZID=Europe/Warsaw, including daylight-saving-time changes.

Additional information

A screenshot showing “Mondays at 9:30 AM · Next run in 11 minutes” was captured at approximately 11:19–11:20 Warsaw time and can be attached before submission.

Related but not identical issue: https://github.com/openai/codex/issues/16938

Please confirm whether this is only a UI next-run calculation bug or whether the automation runner also executes at the UTC-shifted time.

No complete automation configuration is attached because its prompt contains unrelated internal project details.