[UX] Files/screenshots presented in responses are not easily accessible or openable by the user

Problem

When Claude Code presents files (especially screenshots and images) in its responses, users cannot easily access or open them. The specific issues are:

1. File paths are not clickable links — Absolute or relative paths shown in markdown are rendered as plain text or non-functional links in the Claude Code UI (VSCode extension, desktop app, etc.)
2. No quick-open affordance — There is no button, icon, or gesture to open the file in the OS file explorer or default application
3. Path format confusion — Paths may be Windows absolute paths (d:\Github\CIG\...) or relative paths that users don't know how to resolve to their filesystem location
4. Images displayed inline are not saveable — When images are rendered inline in the response, there is no easy way to open them at full resolution or in an external viewer

Impact

This is a recurring UX friction point that affects all workspaces and all workflows where Claude Code captures screenshots or references local files. The user must manually copy the path and navigate to it in Explorer/Finder, or figure out the full path themselves.

Expected Behavior

• File paths in responses should be clickable (deep-link into the editor, or open in OS viewer)
• Images shown inline should have an "open in explorer" or "open externally" affordance
• Or alternatively: Claude Code should copy files to a predictable, well-known output folder (e.g., ~/.claude/screenshots/) and present a consistent relative path

Actual Behavior

Files are presented as non-interactive text or inline images with no clear path to opening them outside the chat UI.

Environment

• Claude Code VSCode Extension
• Windows 11

Reported by user

This issue was reported during a development session where Claude Code captured Unity Game View screenshots via MCP tools and presented them inline. The user could not easily compare the screenshots or open them in an image viewer.