Image paste requires two attempts on Windows -- first attempt always fails with not found
Status Fixed / completed
Reported on v2.1.150
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 3 comments · opened May 25, 2026 · closed May 27, 2026
Description
Pasting an image (Ctrl+V) into Claude Code always fails on the first attempt, then succeeds on the second paste of the same image. This happens 100% of the time, consistently reproducible.
Steps to Reproduce
- Copy any image to clipboard (screenshot, file, etc.)
- Paste into Claude Code input with Ctrl+V
- First attempt fails (image not found / not available)
- Press Ctrl+V again with the same image still on clipboard
- Second attempt succeeds
Expected Behavior
First paste should work without requiring a retry.
Environment
- Claude Code version: 2.1.150
- OS: Windows 11 Pro 10.0.26200
- Shell: PowerShell
Notes
Behavior appears to be a regression — started occurring recently. Likely a timing/race condition where Claude Code checks for the temp file before it has finished being written from the clipboard.
3 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
+1, reproducing this consistently on Windows 11 Pro + Claude Code VSCode extension (Opus 4.7), with Snipping Tool clipboard captures.
Symptom: ~30-50% of pasted screenshots fail with
API Error: an image in the conversation could not be processed and was removed. The image is silently dropped — assistant can't see it, user must re-capture.Repro:
Workarounds that work:
Hypothesis: Snipping Tool writes both PNG and DIB to clipboard with timing delay; extension reads before PNG buffer is fully serialized, gets 0 bytes or partial DIB that fails server-side decode. status.claude.com green during these failures suggests client-side.
Happy to provide more env details if useful.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.