claude-code - 💡(How to fix) Fix Screenshot temp paths no longer readable after v2.1.108 update [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#48077Fetched 2026-04-15 06:33:54
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

Root Cause

Root Cause Investigation

Fix Action

Workaround

Using find + cp to copy the file to /tmp/ works since find handles the Unicode correctly, but this is not a user-friendly workflow.

Code Example

e2 80 af  →  U+202F (narrow no-break space) before "p.m."
RAW_BUFFERClick to expand / collapse

Bug Description

After updating Claude Code to v2.1.108 (updated automatically today April 14, 2026 at 1:14 PM), screenshot file paths pasted into the conversation are no longer readable. The Read tool returns "File does not exist" even though the file was just created.

This worked before the update earlier today.

Steps to Reproduce

  1. Take a screenshot with Cmd+Shift+4 on macOS
  2. Paste the path into Claude Code CLI (path looks like /var/folders/.../TemporaryItems/NSIRD_screencaptureui_.../Screenshot 2026-04-14 at 1.32.37 p.m..png)
  3. Claude Code tries to read the file → fails with "File does not exist"

Root Cause Investigation

Two issues found:

  1. Temp file lifetime: macOS saves screenshots briefly to /var/folders/.../TemporaryItems/ before moving them to the final destination. The file gets deleted before the Read tool executes.

  2. Unicode encoding in filenames: macOS now inserts a Unicode U+202F (narrow no-break space) between the time and "p.m." in screenshot filenames. The path as pasted by the user uses a regular space, causing a mismatch. Verified via xxd:

    e2 80 af  →  U+202F (narrow no-break space) before "p.m."

    Even when the file exists on Desktop, Read and cp fail because the Unicode character doesn't match.

Environment

  • macOS Darwin 25.3.0 (Sequoia/Tahoe), ARM64
  • Claude Code v2.1.108
  • Shell: zsh

Expected Behavior

Claude Code should be able to read screenshot paths pasted by the user, as it did before v2.1.108. Ideally:

  • Handle the U+202F unicode normalization in file paths
  • Or read the temp file fast enough before macOS cleans it up

Workaround

Using find + cp to copy the file to /tmp/ works since find handles the Unicode correctly, but this is not a user-friendly workflow.

extent analysis

TL;DR

Update Claude Code to handle Unicode normalization in file paths or implement a faster file reading mechanism to access temporary files before they are deleted by the system.

Guidance

  • Investigate the possibility of updating the Read tool in Claude Code to correctly handle Unicode characters, such as the U+202F narrow no-break space, in file paths.
  • Consider implementing a mechanism to quickly access and process temporary files before the system deletes them, potentially by monitoring the /var/folders/.../TemporaryItems/ directory for new files.
  • Review the find and cp workaround to understand how it correctly handles Unicode characters and apply similar logic to the Read tool.
  • Test the Read tool with files containing Unicode characters in their names to ensure compatibility and correct handling.

Example

No code example is provided due to the lack of specific implementation details in the issue description.

Notes

The provided workaround using find and cp indicates that handling Unicode characters correctly can resolve the issue, but a more integrated solution within Claude Code is needed for a user-friendly experience.

Recommendation

Apply workaround: The find and cp method demonstrates that correctly handling Unicode characters can solve the problem, so applying this logic to Claude Code's Read tool is recommended until a more permanent fix is available.

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 Screenshot temp paths no longer readable after v2.1.108 update [1 comments, 2 participants]