What version of the Codex App are you using (From “About Codex” dialog)?
Codex App 26.611.61753 (4008) Bundled codex-cli 0.140.0-alpha.19
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
The Codex App automations UI appears to show inconsistent timezones.
I created an automation using the Asia/Tokyo timezone, scheduled for a rounded local time such as 23:00.
The automations list page shows the expected local time, for example:
Weekdays 23:00
However, the automation detail page shows the next run as:
Tomorrow 14:00
14:00 appears to be UTC, because Tokyo 23:00 equals UTC 14:00. The UI does not label it as UTC, so it looks like the automation is scheduled for the wrong local time.
This seems to be a display issue rather than a scheduling issue.
What steps can reproduce the bug?
Feedback ID: 019ed4ac-f754-7af2-8cea-e130eedda0be1. Set the system/user timezone to Asia/Tokyo.
2. Create a Codex App automation using the Asia/Tokyo timezone, scheduled for a rounded local time such as 23:00 on weekdays.
3. Open the Automations list page.
4. Observe that the list shows the expected local time, for example: Weekdays 23:00.
5. Open the automation detail page.
6. Observe that Next run shows Tomorrow 14:00.
Expected:
The automation detail page should show the same local time as the list page, or clearly label the timezone if it is showing UTC.
Actual:
The list page shows Asia/Tokyo local time, but the detail page appears to show UTC time without a timezone label.
What is the expected behavior?
The automation detail page should show the next run time in the same local timezone as the automations list page.
For an automation scheduled at 23:00 Asia/Tokyo, both the list page and detail page should show 23:00 local time, or the detail page should explicitly label the timezone if it is showing UTC.
Additional information
I attached screenshots showing:
- The automations list page showing the expected local time.
- The automation detail page showing a different next run time that appears to be UTC.
The screenshots were cropped to avoid exposing unrelated private information.
What version of the Codex App are you using (From “About Codex” dialog)?
Codex App 26.611.61753 (4008) Bundled codex-cli 0.140.0-alpha.19
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
The Codex App automations UI appears to show inconsistent timezones.
I created an automation using the Asia/Tokyo timezone, scheduled for a rounded local time such as 23:00.
The automations list page shows the expected local time, for example:
Weekdays 23:00
However, the automation detail page shows the next run as:
Tomorrow 14:00
14:00 appears to be UTC, because Tokyo 23:00 equals UTC 14:00. The UI does not label it as UTC, so it looks like the automation is scheduled for the wrong local time.
This seems to be a display issue rather than a scheduling issue.
What steps can reproduce the bug?
Feedback ID: 019ed4ac-f754-7af2-8cea-e130eedda0be1. Set the system/user timezone to Asia/Tokyo.
2. Create a Codex App automation using the Asia/Tokyo timezone, scheduled for a rounded local time such as 23:00 on weekdays.
3. Open the Automations list page.
4. Observe that the list shows the expected local time, for example: Weekdays 23:00.
5. Open the automation detail page.
6. Observe that Next run shows Tomorrow 14:00.
Expected:
The automation detail page should show the same local time as the list page, or clearly label the timezone if it is showing UTC.
Actual:
The list page shows Asia/Tokyo local time, but the detail page appears to show UTC time without a timezone label.
What is the expected behavior?
The automation detail page should show the next run time in the same local timezone as the automations list page.
For an automation scheduled at 23:00 Asia/Tokyo, both the list page and detail page should show 23:00 local time, or the detail page should explicitly label the timezone if it is showing UTC.
Additional information
I attached screenshots showing:
The screenshots were cropped to avoid exposing unrelated private information.