What version of the Codex App are you using (From “About Codex” dialog)?
26.602.71036
What subscription do you have?
ChatGPT Pro 20x / Codex app account with GPT-5.5 access
What platform is your computer?
Darwin 25.5.0 arm64 arm; macOS 26.5 build 25F71
What issue are you seeing?
Codex App automations appear to preserve/display the intended local schedule, but the scheduler's computed next run and actual run time are offset by UTC on a US/Central machine.
Example from the Automations UI for "Singularity Daily Graph Build":
- Automation list says: Daily at 7:00 AM
- Detail panel says: Next run: Tomorrow at 2:00 AM
- Detail panel says: Last ran: Today at 2:01 AM
The underlying automation schedule was a bare RRULE:
FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR,SA,SU;BYHOUR=7;BYMINUTE=0;BYSECOND=0
The app appears to render the summary as 7:00 AM local, while the runner/next-run calculation interprets BYHOUR=7 as 07:00 UTC, which is 2:00 AM CDT.
This affected multiple active automations, not just one automation.
What steps can reproduce the bug?
Feedback ID: 019eab2f-d101-73f0-9290-ea0f0313569e
- On a US/Central machine, create or inspect a local Codex App automation scheduled for 7:00 AM local time.
- Use a custom/daily RRULE schedule like:
FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR,SA,SU;BYHOUR=7;BYMINUTE=0;BYSECOND=0
- Open the Automations list.
- Observe the list summary says "Daily at 7:00 AM".
- Open the automation detail page.
- Observe the detail panel computes the next run as "Tomorrow at 2:00 AM" and recent previous runs as around 2:01 AM.
- Check actual run history. For this automation, recent thread creation/run times were:
- 2026-06-05 07:01 CDT / 2026-06-05 12:01 UTC (correct local behavior)
- 2026-06-06 02:02 CDT / 2026-06-06 07:02 UTC (UTC interpretation starts)
- 2026-06-08 02:02 CDT / 2026-06-08 07:02 UTC
- 2026-06-09 02:01 CDT / 2026-06-09 07:01 UTC
- Check other local automations. The same 5-hour early behavior showed up on schedules intended for 10:30 AM, 7:30 PM, 2:30 AM, and monthly 9:00 AM.
Observed result: BYHOUR appears to be interpreted as UTC for the actual/next run calculation, while parts of the UI still present the intended local schedule.
What is the expected behavior?
Automations scheduled in the Codex App as local times should run at the local time shown in the Automations UI.
For example, a daily automation shown as "Daily at 7:00 AM" on a US/Central machine should compute its next run as 7:00 AM local and should fire around 7:00 AM local, not 2:00 AM local.
Ideally the scheduler should either:
- store/use an explicit IANA timezone such as America/Chicago for local schedules, or
- consistently treat RRULEs as local floating times when the UI says "Runs in: Local".
The behavior should also be DST-safe; users should not need to manually convert local schedules to UTC offsets.
Additional information
The issue seems to be a mismatch between UI schedule labeling and scheduler evaluation. The automation TOML files did not contain a timezone/tzid field. Local workaround was to convert intended Central times to UTC BYHOUR values, e.g. 7:00 AM CDT -> BYHOUR=12, but this is brittle and will be wrong after DST changes or if the runner bug is fixed.
Examples of affected intended schedules:
- Daily 7:00 AM local -> was firing around 2:00 AM CDT
- Weekdays 10:30 AM local -> was firing around 5:30 AM CDT
- Sun-Thu 7:30 PM local -> was firing around 2:30 PM CDT
- Weekdays 2:30 AM local -> was firing around 9:30 PM CDT on the prior evening
- Monthly 9:00 AM local -> fired around 4:00 AM CDT
The UI screenshot showed the list row "Daily at 7:00 AM" while the detail panel showed "Next run Tomorrow at 2:00 AM" for the same automation.
What version of the Codex App are you using (From “About Codex” dialog)?
26.602.71036
What subscription do you have?
ChatGPT Pro 20x / Codex app account with GPT-5.5 access
What platform is your computer?
Darwin 25.5.0 arm64 arm; macOS 26.5 build 25F71
What issue are you seeing?
Codex App automations appear to preserve/display the intended local schedule, but the scheduler's computed next run and actual run time are offset by UTC on a US/Central machine.
Example from the Automations UI for "Singularity Daily Graph Build":
The underlying automation schedule was a bare RRULE:
The app appears to render the summary as 7:00 AM local, while the runner/next-run calculation interprets BYHOUR=7 as 07:00 UTC, which is 2:00 AM CDT.
This affected multiple active automations, not just one automation.
What steps can reproduce the bug?
Feedback ID: 019eab2f-d101-73f0-9290-ea0f0313569e
Observed result: BYHOUR appears to be interpreted as UTC for the actual/next run calculation, while parts of the UI still present the intended local schedule.
What is the expected behavior?
Automations scheduled in the Codex App as local times should run at the local time shown in the Automations UI.
For example, a daily automation shown as "Daily at 7:00 AM" on a US/Central machine should compute its next run as 7:00 AM local and should fire around 7:00 AM local, not 2:00 AM local.
Ideally the scheduler should either:
The behavior should also be DST-safe; users should not need to manually convert local schedules to UTC offsets.
Additional information
The issue seems to be a mismatch between UI schedule labeling and scheduler evaluation. The automation TOML files did not contain a timezone/tzid field. Local workaround was to convert intended Central times to UTC BYHOUR values, e.g. 7:00 AM CDT -> BYHOUR=12, but this is brittle and will be wrong after DST changes or if the runner bug is fixed.
Examples of affected intended schedules:
The UI screenshot showed the list row "Daily at 7:00 AM" while the detail panel showed "Next run Tomorrow at 2:00 AM" for the same automation.