Sent file attachments render as empty, non-clickable chips (no preview, click does nothing) — desktop, Windows

Resolved 💬 2 comments Opened Jun 20, 2026 by oscardcstudio-cell Closed Jun 24, 2026

Summary

Files delivered to the user via the "send files" mechanism render as an empty, non-clickable chip in the desktop client. The chip shows the filename and size (e.g. nano-doute-textonly.png · 364.4 KB) but:

  • no thumbnail / preview is shown
  • clicking the chip does nothing (cannot open, preview, or download the file)

The underlying file is a perfectly valid image (verified: a 364 KB PNG that opens fine in any external viewer). So the file transfer works, but the client-side chip is dead — the user cannot actually view what was sent.

Steps to reproduce

  1. Have the agent send an image file to the user (generated PNG, ~300–500 KB, 4:5).
  2. Observe the attachment chip that appears in the conversation.

Expected

The attachment chip should preview the image (thumbnail) and/or be clickable to open/download it.

Actual

The chip displays only an icon + filename + size. It is not clickable and shows no preview. The user has no way to view the file from the chip; the only workaround is opening the file from disk via an external command.

Environment

  • Claude Code, desktop app
  • OS: Windows 11 (10.0.26200)
  • File type tested: PNG, ~364 KB, generated locally to a temp path

Impact

Any agent workflow that produces a visual deliverable (generated images, screenshots, rendered slides, charts) is effectively broken for review: the user is told a file was delivered but cannot see it.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗