Description

The usage dashboard date filter appears to use UTC for day boundaries instead of the user's configured timezone. When filtering for "Today" or a specific date range, sessions that occurred in the local evening (e.g., 6 PM - midnight MST) may not appear until the next UTC day rolls over, or may be split across two dashboard days.

Steps to Reproduce

1. Configure a user timezone (e.g., America/Denver / MST, UTC-7)
2. Run some agent sessions in the local evening (e.g., 8 PM MST = 3 AM UTC next day)
3. Open the usage dashboard and set the date filter to today's date
4. Observe that evening sessions may not appear, or appear under tomorrow's date
5. Expand the date range by one day — the "missing" sessions appear

Expected Behavior

The date filter should respect the configured user timezone (agents.defaults.userTimezone or the system-level timezone). A session at 8 PM MST on Feb 15 should appear under Feb 15 when filtering by date.

Actual Behavior

Date boundaries appear to be midnight UTC. Sessions in the local evening get attributed to the next day in the dashboard, or are excluded when filtering for "today."

Environment

• OpenClaw version: 2026.2.13
• Configured timezone: America/Denver (UTC-7)
• OS: macOS (Darwin 25.3.0 arm64)
• Dashboard accessed via webchat control UI