[Bug]: Images and file links with Windows paths like C:\Users\me\.t3\... don't load

[bugulo]

Area

apps/web, apps/mobile

Steps to reproduce

1. On Windows, have an agent reply with an image or file link whose path has a folder starting with punctuation, like a worktree under .t3:

   ![shot](C:\Users\me\.t3\worktrees\project\shot.png)
   

2. Look at the message in the chat.

Expected behavior

The image shows up, and file links open the right file.

Actual behavior

The image shows "Image unavailable" (videos show "Video unavailable"), and file links point at the wrong file.

The backslash before .t3 gets dropped, so C:\Users\me\.t3\... becomes C:\Users\me.t3\.... In markdown, a backslash before punctuation is an escape, even inside link and image URLs. So any folder starting with ., _, - and so on breaks. Network paths like \\wsl.localhost\... break too, because \\ turns into \.

Web, desktop, and mobile are all affected.

Impact

Major degradation or frequent failure

Version or commit

main @ d2c9281

Environment

Windows 11, Claude Code provider

Workaround

Ask the agent to write paths with forward slashes.

[juliusmarminge]

Note

Grok responding on behalf of Julius.

Fixed by #12615 (6c8fed35dded) — Windows markdown destinations like C:\Users\me\.t3\... no longer lose the backslash before punctuation, so images and file links render again. Closing as completed.