VS Code extension 2.1.272: chat file links with non-ASCII (Korean) path components no longer open (regression from 2.1.270)
Summary
Since VS Code extension 2.1.272 (installed 2026-09-15), clicking a file link in the chat panel does nothing when the path contains non-ASCII (Korean) characters — in a directory name or in the file name. The same links opened fine on 2.1.270 and earlier (confirmed working on 2026-09-13).
Environment
- Claude Code VS Code extension 2.1.272 (darwin-arm64); previous 2.1.270 worked
- Claude Code CLI 2.1.261
- VS Code 1.137.0, macOS 26.6.2
- Multi-root workspace; the target folder is one of the workspace folders (so this is not an "outside workspace" restriction)
Reproduction
Have Claude output markdown links to existing files. Click each in the chat panel.
| Link path | Result |
|---|---|
| /Users/me/Workspace/proj/CLAUDE.md (ASCII, in workspace) | opens |
| /Users/me/Workspace/Other/AI-Factory/security-process.md (ASCII, different workspace folder) | opens |
| /Users/me/Workspace/Other/보안인증/Cert/README.md (Korean directory in path) | nothing happens |
| /Users/me/Workspace/Other/Cert/01_보안기능_구현명세서.md#L100 (Korean file name) | nothing happens |
| Same path with the Korean segments percent-encoded (%EB%B3%B4...) | nothing happens |
| code -g "/Users/me/Workspace/Other/보안인증/Cert/01_보안기능_구현명세서.md:100" from a terminal | opens (so the file/path is fine) |
Workaround that proves the diagnosis: an ASCII-named symlink to the same file (/Users/me/links/03.md -> /Users/me/Workspace/Other/Cert/03_자체_시험_결과_보고서.md) opens from the chat link, #L line anchor included.
Expected
Links to files with non-ASCII path components open in the editor (as they did on 2.1.270), with or without a #Lnn anchor.
Notes
- No error is shown; the click is silently ignored.
workbench.editorAssociationshas no*.mdentry, so it is not an editor-association issue.- Korean file names are the norm for our team's documents, so the regression blocks the "click line reference to jump" flow for every document we work on.