You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Codex Desktop Profile token activity shows next day instead of local date #25762
Local timezone/location: California, United States
What issue are you seeing?
The Profile page's Token activity calendar/usage heatmap appears to have a date/timezone synchronization bug.
My computer's local date is currently Jun 1 in California time, but the Token activity heatmap marks the current/hovered day as Jun 2. The tooltip shows:
0 tokens on Jun 2
This makes the daily usage display appear one day ahead of the user's actual local date.
Steps to reproduce
Open Codex Desktop.
Go to Settings/Profile.
Look at the Token activity daily heatmap.
Hover over the current day's square near the right side of the chart.
Compare the tooltip date with the computer's actual local date.
Expected behavior
The Token activity chart should use the user's local system timezone/date when displaying daily usage. If the user's computer is currently on Jun 1 in California time, the current day's activity square and tooltip should show Jun 1, not Jun 2.
Actual behavior
The Token activity chart shows the current activity square as Jun 2 even though the local computer date is still Jun 1.
Why this matters
Daily usage tracking needs to align with the user's local date. Showing the next day early can confuse users about when tokens were used, whether usage is being counted for the correct day, and whether streak/activity data is accurate.
This looks like the chart may be using UTC/server date boundaries instead of the user's local timezone, or otherwise applying an incorrect timezone conversion when rendering the daily Token activity heatmap.
I can reproduce the same issue on Windows in Asia/Taipei (UTC+8). I used Codex on 2026-09-11 from 06:04 to 07:36 local time. In Codex Desktop Profile > Token activity, 2026-09-11 showed 0 tokens and the activity appeared under 2026-09-10, which broke my activity streak.
A read-only account/usage/read check returned a bucket for 2026-09-10 and no bucket for 2026-09-11. This is consistent with the daily activity being bucketed by UTC rather than the user's local calendar date.
Expected behavior: the profile heatmap and streak should use the user's local timezone, or the UI should explicitly label UTC and avoid treating local activity as a missed day.
Activity
bestdrduck commentedon Sep 12, 2026
I can reproduce the same issue on Windows in Asia/Taipei (UTC+8). I used Codex on 2026-09-11 from 06:04 to 07:36 local time. In Codex Desktop Profile > Token activity, 2026-09-11 showed 0 tokens and the activity appeared under 2026-09-10, which broke my activity streak.
A read-only account/usage/read check returned a bucket for 2026-09-10 and no bucket for 2026-09-11. This is consistent with the daily activity being bucketed by UTC rather than the user's local calendar date.
Expected behavior: the profile heatmap and streak should use the user's local timezone, or the UI should explicitly label UTC and avoid treating local activity as a missed day.