Understand Image Paste Storage and Provider Boundaries

An attached screenshot is data, not decoration. Before pasting it into Hermes, understand both the local storage path and the model route that may receive its pixels or a derived description.

Follow the image data path

Hermes can attach an image from the clipboard or a file path. Attached images are saved locally as timestamped PNG files under the Hermes images directory. They are not automatically “temporary” merely because they entered through the clipboard.

When the active model supports vision, Hermes sends the image as native image content. When the active model is text-only, the vision analysis tool can route the image through a configured auxiliary vision model and inject the resulting description into the conversation.

That means the relevant privacy boundary may include the active provider or an auxiliary provider. Check routing before attaching sensitive pixels.

Redact before attachment

Remove or mask:

• passwords, tokens, recovery codes, and QR credentials;
• customer records and private messages;
• browser tabs, notifications, and account names;
• private hostnames, paths, and internal URLs;
• faces, addresses, and location details that are not needed; and
• hidden metadata when sharing the saved file elsewhere.

Crop to the smallest area that proves the issue. A whole desktop screenshot is rarely necessary.

Safe-attachment checklist

• The active and auxiliary vision providers are known.
• The screenshot is cropped to the relevant region.
• Secrets and private identifiers are redacted in the pixels.
• The saved local image is stored in an appropriate profile/home scope.
• Multiple attachments are intentional and individually reviewed.
• The prompt states exactly what should be inspected.

Common pitfalls

Redacting text in the prompt but not the pixels

The model receives the image content. Replacing a name in your question does not alter the screenshot.

Assuming a text-only model means no image provider

Hermes may use an auxiliary vision model to describe the image for a text-only active model.

Forgetting local persistence

Pasted images are saved locally. Review retention and file permissions when screenshots contain sensitive information.

Verification steps

1. Check the configured active model and vision route.
2. Attach a harmless test image.
3. Confirm the attachment badge appears before sending.
4. Verify the saved image location and permissions locally.
5. Ask a narrowly scoped visual question.
6. Confirm the response reflects the intended image and no unrelated screen area.
7. Remove test artifacts when they are no longer needed.

Official reference

Read Vision & Image Paste for current attachment methods, platform behavior, and model routing.