[BUG] VS Code extension: file links in the plan approval view do nothing when clicked (Windows)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Steps to reproduce

1. In plan mode, have Claude write a plan with markdown links to workspace files, e.g. [foo.component.ts](src/app/foo.component.ts).
2. Claude calls ExitPlanMode, which opens the plan approval view.
3. Click a file link.

Expected

The file opens in a new editor tab, as it does for links in Claude's chat replies.

What Should Happen?

The file opens in a new editor tab, as it does for links in Claude's chat replies.

Error Messages/Logs

The link is rendered as a link (underlined, link colour), but clicking it does nothing. There is no error and no tab opens.

Steps to Reproduce

1. In plan mode, have Claude write a plan with markdown links to workspace files, e.g. [foo.component.ts](src/app/foo.component.ts).
2. Claude calls ExitPlanMode, which opens the plan approval view.
3. Click a file link.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.284

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

These link formats all fail in the plan approval view:

| Link format | Result |
|---|---|
| src/... (repo-relative) | nothing happens |
| /C:/<workspace>/<repo>/src/... | nothing happens |
| ../../../../<workspace>/<repo>/src/... (relative to the plan file) | nothing happens |
| file:///c:/<workspace>/<repo>/src/... | nothing happens |

All target files exist on disk. I checked each path from the plan file's folder.

Related behaviour in the same session

• The same repo-relative links open correctly from Claude's chat replies.
• If the plan .md is opened directly in the editor, the repo-relative links resolve against ~/.claude/plans/, because the plan file lives outside the workspace, so clicking them gives file not found.
• In the same case, the /C:/... form gives "The editor could not be opened because the file was not found", even though the file exists.

Impact

Plans point to the files they change. Without working links, the user has to find every file by hand while reviewing, and the only workaround is asking Claude to repeat the file list as links in chat.

Possibly related

• #89829: VS Code extension: some file links on Windows do nothing when clicked. It covers inert absolute Windows path links in chat, but not the plan approval view.
• #91129: file-path links resolve against the wrong base folder.