# NousResearch/hermes-agent · Timezone awareness and user timezone configuration

## Open now

- Nothing open on GitHub.

These issues and pull requests concern adding native timezone support to Hermes, including anchoring cron schedules, prompts, and code execution to a configured timezone rather than defaulting to UTC. Both feature requests and fixes are represented.

## TL;DR

- 3 member(s): 0 open issue(s), 3 closed issue(s), 0 open PR(s), 0 merged PR(s), 0 PR(s) closed without merging.
- No fix found: no merged or attempted fix PR is on record for this cluster.
- **Recommended:** if this matches your symptom, consider adding to the existing issue(s) below rather than opening a new one.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`LLM_ONLY`): no structural link between members; the grouping rests entirely on an automated relevance judgement over their text.
- Read the members yourself before treating them as one problem.
- Pairwise link density `0.36`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #16610: feat: 支持用户自定义时区设置
- #26255: \[Feature\]: Native user timezone configuration — Hermes should default to user's timezone, not UTC
- #26976: Feature Request: Native timezone support for user-facing timestamps

## Fix status

- No merged fix on record.
- Subsystem: `agent`