hermes - 💡(How to fix) Fix Feature Request: Native timezone support for user-facing timestamps

Description

When a user is in a non-UTC timezone (e.g., America/Los_Angeles), all timestamps shown in agent responses should be automatically converted to the user's local timezone.

Currently, the agent must rely on memory entries like "always convert to Pacific Time" but consistently fails to apply this during execution. The cron scheduler uses UTC (which is correct), but the agent reports UTC times to the user without converting.

Proposed solution

Add a user.timezone config setting (e.g., in config.yaml or the user profile) that the agent framework enforces on all time output. When set, the agent automatically converts all UTC timestamps to the user's local timezone before displaying them.

Example config

user:
  timezone: America/Los_Angeles

Use case

A user in Pacific Time repeatedly asks the agent to "always use Pacific Time." The agent saves this to memory and acknowledges it, but continues to report times in UTC because the conversion requires active reasoning on every timestamp output. A native timezone setting would eliminate this class of errors.

Environment

• Hermes Agent running on Ubuntu VPS (UTC)
• User communicating via Telegram from America/Los_Angeles (PDT/UTC-7)
• Cron scheduler uses UTC (correct), but agent responses don't convert