7 people reported
All time, since Sep 15, including 3 thumbs-up on GitHub.
Non-ASCII file links don't open
“There is no notification, no error, and no file opens.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/1365/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Chat file links with non-ASCII paths do nothing when clicked. In the VS Code extension chat panel, clicking links to Korean or CJK paths gives no error, no notification, and opens no file.
Is this your bug?
File my report- Where
- VS Code extension
- Versions
- 2.1.261
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow. Some reports say it used to work.
Original reports4, newest first
- Chat file links to non-ASCII (CJK) paths are silently no-ops (click does nothing)#97542
- VS Code extension: chat file links with spaces / non-ASCII paths never open — host never percent-decodes (fix location + workaround inside)#96612
- VS Code extension 2.1.272: chat file links with non-ASCII (Korean) path components no longer open (regression from 2.1.270)#94648
- VS Code extension: markdown file links in chat do not open when the path contains non-ASCII (Korean) characters — still reproducible in 2.1.270#94449