Windows: delivered file cards have no Show in Explorer / Open / Copy path action

Preflight

• Searched existing issues: #65677 (closed/completed, platform:macos), #67510 (closed as duplicate of it, now locked), #78649 (open, macOS framing), #84550 (open).

Problem Statement

On Windows, a file delivered by an agent (SendUserFile) renders as a card in the chat with no way to reach the file on disk. There is no "Show in Explorer", no "Open containing folder", no "Copy path" — so the only route is reading the path out of the surrounding text and pasting it into Explorer by hand.

This bites hardest because agent working files live in the session scratchpad:

C:\Users\<me>\AppData\Local\Temp\claude\<project-hash>\<session-id>\scratchpad\

That is not a path anyone navigates to casually. In a real session my agent delivered an HTML diagnostic it wanted me to open in a different browser on a different machine; getting it out of the chat was several manual steps, and we ended up publishing it as an Artifact purely to sidestep the file card.

The clickable-chip fix in #65677 appears to have landed for macOS only (that issue and its duplicates are all labeled platform:macos). Windows has no equivalent affordance.

Proposed Solution

Give the file card a context menu on Windows with the same actions the macOS fix provides:

• Show in Explorer — explorer.exe /select,<path>, opening the folder with the file highlighted
• Open — launch in the OS default application
• Copy path — put the absolute path on the clipboard

"Show in Explorer" is the important one: it hands the file to the user's own file manager, where they can drag, copy, rename, or open it however they like, and it works regardless of file type.

Alternative Solutions

• Make the card itself clickable to open the file (the macOS behavior). Better than nothing, but a reveal-in-folder action is more useful for files the user wants to move or send elsewhere.
• Have agents write deliverables to a well-known folder (Downloads) and reveal them from the shell. This is the workaround in use today: the agent runs explorer.exe /select,<path> on request. It works, but it requires knowing to ask, and it makes the file card decorative.

Priority

Medium — there is a workaround, but it costs a round-trip every time a file is handed over.

Feature Category

Desktop app / UI

Use Case Example

1. In Claude Code in the Windows desktop app, have an agent deliver a file with SendUserFile (e.g. an HTML page it wants you to open in a specific browser).
2. A file card appears in the chat.
3. Right-click it.

Expected: a menu offering Show in Explorer / Open / Copy path.
Actual: no menu with those actions; the file is reachable only by retyping the scratchpad path.

For comparison, Codex's file output offers a right-click "open in Explorer" option, which makes handing a file back to the user a single click.