claude-code - 💡(How to fix) Fix Regression in v2.1.140: Windows absolute file-path paste no longer attaches as image [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#58658Fetched 2026-05-14 03:42:42
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×4cross-referenced ×2commented ×1

Fix Action

Fix / Workaround

Net effect

With both binary-paste and filename-paste broken, there is currently no working path to attach a screenshot on Windows without WSL. Filename-paste was effectively the only working Windows workaround and v2.1.140 removed it.

RAW_BUFFERClick to expand / collapse

Environment

  • Windows 11 Pro
  • Claude Code CLI v2.1.140 (npm global install, not WSL)
  • Windows Terminal

Previous behavior (through v2.1.139)

Pasting a Windows absolute file path like C:\path\to\screenshot.png into the Claude Code prompt would attach the referenced file as [Image #1]. The model received the image as a multimodal attachment and could see it.

Workflow:

  1. Snipping Tool rectangle capture
  2. Save to a folder under the project cwd
  3. Copy the full filename during the Save dialog
  4. Switch to Claude Code, Ctrl+V → [Image #1] chip appears

Current behavior (v2.1.140)

Same Ctrl+V paste inserts the absolute path as literal text. No attachment, no chip. Claude only sees the path string.

Sanity checks ruling out other causes

  • Binary clipboard paste (Snipping Tool → Ctrl+V the bitmap directly, without saving) also produces nothing in Claude Code on Windows — appears to be the same class of issue as #22068.
  • Same clipboard contents paste correctly into Outlook, confirming the bitmap is actually on the Windows clipboard.
  • @<path> syntax is text-only — inlining a binary PNG corrupts it; not a viable substitute.

Net effect

With both binary-paste and filename-paste broken, there is currently no working path to attach a screenshot on Windows without WSL. Filename-paste was effectively the only working Windows workaround and v2.1.140 removed it.

Likely cause

The v2.1.140 changelog mentions a fix for "pasting/dropping multiple images only inserting the last one." That change appears to have tightened image-clipboard detection in a way that also dropped the filename-text fallback that Windows users were relying on.

Suggested fix

Either:

  • Restore the filename-text-as-image-path heuristic on Windows, or
  • Make Windows binary clipboard paste work (the more general fix; would also close #22068), or
  • Add explicit @<path> attach syntax for images that recognizes image extensions and attaches as multimodal rather than inlining as text.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Regression in v2.1.140: Windows absolute file-path paste no longer attaches as image [1 comments, 2 participants]