NousResearch/hermes-agent

Windows timezone fix for code-execution child processes

Cluster 112233. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #113166 on 17 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #113166. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #113166. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #113166, then check it covers your case.

Read #113166 Pick up a Lab task

These items address a bug where child processes spawned for code execution on Windows report the wrong local time when an IANA timezone name is configured, because Windows CPython cannot parse IANA names passed via the TZ environment variable. The members cover the bug report and related fix attempts.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#113166 fix(tools): Windows execute_code children keep the correct local time when a timezone is configured (#112233, salvage #112261)

merged to main

files: tests/tools/test_code_execution.py, tests/tools/test_code_execution_windows_env.py, tools/code_execution_env.py, website/docs/reference/environment-variables.md, website/docs/user-guide/configuration.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/reference/environment-variables.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/configuration.md

1 PR closed without merging

From the close comments: superseded by another PR 1

#112261 fix(tools): preserve Windows code child local timezone · superseded by another PR → #113166, #112261

Closed issues · 1

Closed#112233Windows: code-execution children report a wrong local time when `timezone:` is configured — an IANA name is handed to `TZ`, which Windows CPython cannot parse

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs: #113166
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 17 Sep 2026

For your agent

The same facts, typed.

cluster/112233.json
cluster/112233.md