RELIABILITY BRIEF · P2 · DESKTOP / VISION
Hermes Desktop Attachment Persistence Across Session Changes: Issue #70772
A sourced reliability brief on an open desktop report in which attached images can reorder after session switching or disappear from history after a restart.
What the report says
The issue report describes two attachment-persistence failures in the desktop app: image and text layout can reorder when a user switches sessions and returns, and an image can disappear from history after a full application restart, leaving only a caption or stub. The report frames this as a session-state and vision attachment integrity problem.
Status boundary: This brief summarizes a public, open issue report. It is not an independent reproduction, security assessment, product-wide reliability estimate, or confirmation that the report remains unresolved.
Operational significance
For affected users, a missing or detached image can change the meaning and auditability of a conversation, particularly where visual context supports a decision or tool-assisted task. This page reports the issue as open and does not claim frequency, data-loss scope, or behavior across all desktop versions and operating systems.
Evidence-bounded verification checklist
| Check | Question | Safe evidence practice |
|---|---|---|
| Initial attachment | Does a new image appear with its intended text and position? | Record the session, client version, attachment type, and visible message order. |
| Session round trip | Does switching away and back preserve image, text, and ordering? | Repeat with a non-sensitive sample attachment and capture a before-and-after state. |
| Restart persistence | After a clean restart, does history retain the attachment and association? | Distinguish a rendering absence from confirmed storage loss where evidence permits. |
| History consistency | Do transcript, preview, and message metadata agree on the attachment? | Report mismatches without inferring the underlying storage mechanism. |
| User-facing recovery | Can a user identify what is missing and recover safely? | Avoid destructive cleanup until the current session and history state are preserved. |
Handling guidance
- Use non-sensitive sample images while reproducing or documenting the issue.
- Preserve session identifiers, timestamps, client build, and clear before-and-after screenshots where safe.
- Do not equate a visual rendering change with permanent deletion unless the available evidence demonstrates it.
- Track the upstream issue for confirmation, reproduction steps, and any release note that changes the status.
Source evidence
Hermes Agent GitHub issue #70772
Issue status, labels, discussion, and remediation guidance can change. Consult the upstream report directly before making deployment or product decisions.