VSCode extension: clickable file links with spaces in the path do not open from the chat panel

Open 💬 0 comments Opened Jun 22, 2026 by fkamke

Environment

  • Claude Code VSCode extension v2.1.185
  • macOS (Darwin 25.x)
  • Workspace contains folders with spaces in their names (e.g. Some Folder/…)

Description
File links rendered in the Claude chat panel do not open when the file path contains spaces. Links without spaces work correctly, so link-opening itself is functional — the failure is specific to spaces in the path.

Steps to reproduce

  1. Open a workspace that has a folder with a space in its name, e.g. Some Folder/sub dir/example.js.
  2. Have Claude render a markdown file link to it in the chat. Tried all of these:
  • [x](Some Folder/...) → raw spaces: markdown renders no link at all
  • [x](Some%20Folder/...) → renders a link, but clicking does nothing
  • [x](<Some Folder/...>) → renders a clickable link, but clicking does nothing
  • absolute path, ./ prefix, and file:// variants → same failure
  1. Click the rendered link in the chat panel.

Expected
The file opens in the editor (as it does for paths without spaces).

Actual
Nothing happens. The resolver appears to neither URL-decode %20 nor handle raw spaces.

Key evidence that this is an extension bug, not a markdown/syntax issue
The identical link [example.js](<Some Folder/sub dir/example.js>) placed in a normal .md file opens correctly — VSCode's own markdown link handler resolves the spaces fine. The same link rendered in the Claude chat panel does not open. Same syntax, same file; only the renderer/resolver differs.

Likely fix
URL-decode the href (and/or handle raw spaces) in the chat panel's link resolver before passing the path to the editor-open call, matching VSCode's native markdown link behavior.

View original on GitHub ↗