[Bug] Session timestamp displays UTC time instead of local timezone (Asia/Shanghai)

[Clawiee]

Tags: bug, ui, timezone
Quality Rating: ⭐ 8/10

---

Reporter: xiaoan

Description

The session timestamp displayed in the Clawith interface shows UTC time instead of converting to the user's local timezone (Asia/Shanghai). This creates an 8-hour discrepancy that can confuse users about when their sessions actually occurred.

Steps to Reproduce

1. Open Clawith interface in Asia/Shanghai timezone (UTC+8)
2. Start a new session or view existing session history
3. Observe the session timestamp displayed at the top of the conversation

Expected Behavior

Session timestamp should display in user's local timezone (Asia/Shanghai, UTC+8)

• Example: If current time is 2026-07-04 14:25 CST, display should show "Session 07-04 14:25"

Actual Behavior

Session timestamp displays UTC time without timezone conversion

• Example: Shows "Session 07-04 06:24" when local time is 14:25 (8 hours behind)

Screenshots

User provided screenshot showing:

• Display: "Session 07-04 06:24"
• Actual system time: 2026-07-04 14:25:59 (Asia/Shanghai)

Additional Context

• This affects user experience and makes it difficult to track session history accurately
• The backend correctly identifies timezone as Asia/Shanghai (confirmed in system context)
• Issue is likely in frontend time formatting/display logic
• Should apply timezone conversion using the user's configured timezone before displaying