Desktop (Windows): file links are not clickable when the file is on a different drive than the session cwd

Environment

• Claude Code Desktop 2.1.225, Windows 11 Pro for Workstations (10.0.26200)
• Session working directory on C: (e.g. C:\Users\me), project files on another drive (e.g. D:\Projects\tool)

Behavior

The assistant renders file references as markdown links so they can be clicked to open. This works for paths relative to the session cwd, but when the referenced file lives on a different drive, clicking the link does nothing.

The system prompt tells the model to use "the path relative to the working directory as the href" — but on Windows a path on another drive (D:\... vs cwd on C:) has no relative form, so the model can only emit an absolute href like [label_gui.py](D:\Projects\tool\label_gui.py), which the renderer apparently doesn't resolve as a local file (and it isn't a valid URI either). Result: dead links for any multi-drive workflow, which is common on Windows (code on a data drive, cwd elsewhere).

Repro

1. Start a Desktop session with cwd on C:.
2. Have the assistant reference a file on D: as a markdown link (absolute path href).
3. Click the link — nothing happens.

Expected

Absolute local Windows paths (drive-letter or file:// form) in assistant-rendered links open in the editor/file manager, same as relative paths do.