Hindsight plugin timezone fix for retain timestamps
NousResearch/hermes-agent · cluster 46424 · agent
Data as of
Nothing open on GitHub. Fix merged in #119888. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #119888. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where the Hindsight plugin hardcoded UTC timestamps in retain payloads instead of using the local timezone. The work also bundles a Discord tool_search deferral fix and a thread rename change.
Open issues0
Open PRs0
Fixes on record
-
#119888 hindsight moves to the plugin catalog (auto-migrated on first start / hermes update)
files:
.github/workflows/tests-os.yml,.github/workflows/tests.yml,COMPAT_MANIFEST.md,CONTRIBUTING.es.md,CONTRIBUTING.md,Dockerfile,compat_manifest.json,hermes_cli/config_defaults.py,hermes_cli/memory_setup.py,hermes_cli/subcommands/memory.py,hermes_cli/tips.py,hermes_cli/update_cmd.py,hermes_cli/web_server_memory.py,nix/checks.nix,nix/hermes-agent.nix,nix/moduleCommon.nix,nix/packages.nix,plugins/AGENTS.md,plugins/memory/__init__.py,plugins/memory/hindsight/README.md(+30 more)
4 PRs closed without merging
From the close comments: duplicate 2 · done elsewhere 1 · superseded by another PR 1
- #46436 fix(hindsight): use local timezone in retain payload timestamps · duplicate
-
#46437 fix(hindsight): use local timezone in retain timestamps · done elsewhere →
9d799e0,4cbf862,dc75038,97850af,497d6d5,#119888,#46436 -
#46449 fix: hindsight local timestamps + discord tool_search deferral + rename_thread (#46424, #46400, #46396) · superseded by another PR →
#48207,#48208,#48209 -
#48207 fix(hindsight): use local timezone in retain payload timestamps · duplicate →
#46436
Closed issues · 1
- Closed#46424[Bug]: Hindsight plugin hardcodes UTC timestamps in retain payload — downstream memory extraction loses local timezone
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.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #119888
- Closed issues
- 1
- Attempts
- 4 PRs closed without merging
- Fix link checked
- 23 Sep 2026