Desktop artifact timestamp and indexing bug fixes
Cluster 41142 · apps/desktop. Data as of
2 open items. Fix merged in #86749 on 15 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 19 related items grouped here, 5 issues already closed.
- Fix event
- A fix was merged to main in PR #86749. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PR #86749. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read #86749, then check whether your report is the one still open.
Read #86749Pick up a Lab taskThese issues and PRs address incorrect artifact timestamps displaying as Jan 1970 or Jan 21 dates, caused by epoch seconds being passed to a milliseconds-expecting Date constructor. Several members also cover related over-indexing of non-artifact page references in the desktop artifacts panel.
Open issues1
- Issue#47394[Feature]: Date/Time Consistency
Open PRs1
- PR#41156fix(desktop): clean up artifacts indexing
Fixes on record
-
#86749 fix(desktop): artifacts panel 1970 timestamps, over-indexing, and local image display
files:
apps/desktop/src/app/artifacts/artifact-utils.ts,apps/desktop/src/app/artifacts/index.test.ts,apps/desktop/src/app/artifacts/index.tsx,contributors/emails/[redacted:email]
11 PRs closed without merging
From the close comments: done elsewhere 5 · duplicate 2 · closed without comment 1 · merged via another change 1 · superseded by another PR 1 · other 1
-
#42415 fix(desktop): convert epoch seconds to ms in artifact timestamp rendering · done elsewhere →
#86749,#42221 -
#42618 fix(desktop): format artifact epoch seconds · done elsewhere →
#86749,#42221 -
#42670 fix(desktop): fix artifact timestamps rendering as jan 1970 · done elsewhere →
#86749,#42221 - #45095 fix(desktop): Desktop artifact timestamps display incorrect date (Jan 21 instead of actual date) (#45050) · closed without comment
-
#48433 fix(desktop): normalize epoch seconds to milliseconds in Artifacts timestamp · duplicate →
#42221
Show 6 more
-
#48442 fix(desktop): convert epoch seconds to milliseconds in formatArtifactTime · superseded by another PR →
#42415 -
#48513 fix(desktop): treat artifact timestamps as epoch seconds, not milliseconds · duplicate →
#42415 -
#48577 fix(desktop): clean artifacts timestamps and browser assets · done elsewhere →
#86749,#42221 -
#49091 fix(desktop): normalize artifact timestamps · done elsewhere →
#86749,#42221 - #81895 superseded by #81954: Desktop artifact indexing fix · other
-
#81954 fix(desktop): stop artifact over-indexing and repair dates · merged via another change →
#86749
Closed issues · 5
- Closed#41142Hermes Desktop Artifacts over-indexes path references and displays Unix-second timestamps as Jan 21
- Closed#42409Desktop Artifacts: all timestamps render as Jan 1970 (epoch seconds passed to a millisecond Date constructor)
- Closed#45050Desktop artifact timestamps display incorrect date (Jan 21 instead of actual date)
- Closed#48350[Bug]: Desktop Artifacts page displays session timestamps as Jan 1970-era dates and indexes non-artifact page images
- Closed#51321[Bug]: "artifacts" 视图BUG
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.13: 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
- apps/desktop
- Merged PRs
- #86749
- Closed issues
- 5
- Attempts
- 11 PRs closed without merging
- Fix link checked
- 15 Aug 2026