Automation UI shows UTC time as local time and labels finite schedules as “Daily” without exposing schedule details

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

26.903.61454

What subscription do you have?

pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Issue 1: Displayed schedule and actual execution use different timezones
The automation card displayed “Daily at 00:14”, without a timezone label.
The scheduler’s stored next execution time was 08:14:44 in the system’s local timezone. The automation actually triggered at 08:15:09 local time.
The eight-hour difference matches the system timezone’s UTC offset. This suggests that the scheduler interprets the scheduled hour as UTC, while the UI displays it without converting to local time or labeling it as UTC.
The additional approximately 25-second delay after the stored execution time is separate from the timezone mismatch.
Issue 2: Finite schedules are misleadingly labeled “Daily”
This was intended as a one-time test, with an explicit schedule expiration. However, the card displayed “Daily,” implying indefinite recurrence.
Opening the automation’s details did not expose enough information to verify:

• The timezone used for execution.
• The expiration date/time.
• Whether the schedule is finite or recurring indefinitely.
• The remaining scheduled occurrences.
  This also makes schedules intended to execute only once or twice difficult to verify.

What steps can reproduce the bug?

Steps to reproduce

1. Use a system configured with a non-UTC timezone.
2. Create an automation with a daily recurrence rule and an expiration allowing only one occurrence.
3. Inspect the automation card and its details.
4. Compare the displayed time with the scheduler’s next execution time and actual trigger time.

What is the expected behavior?

Display execution times consistently in the system’s local timezone, with an explicit timezone label.
Show a one-time schedule as “Once, [date/time/timezone]”.
For finite recurring schedules, show the expiration or remaining occurrences.
Expose the effective schedule and next execution time in the details view.

Additional information

The card displayed an unlabeled UTC hour, while execution occurred eight hours later in local time.
A finite one-time test was labeled “Daily.”
The details view did not provide enough information to resolve either ambiguity.
Evidence
Attached screenshot: the automation card displays “每天 0:14” (“Daily at 00:14”).
Verified timing:

• Displayed time: 00:14
• Stored next execution: 2026-09-14T08:14:44+08:00
• Actual trigger: 2026-09-14T08:15:09.554+08:00

Start at the Automation card and details view, then trace the scheduler's stored next execution time and recurrence or expiration data. Compare the displayed timezone and schedule label with the verified execution values; done means local times are labeled consistently and finite schedules expose their effective details.