[Windows] Dispatch "output" button fails with "Location is not available" — junction path blocked by Explorer

Description

On Windows, clicking the "output" button in Claude's Dispatch panel throws a "Location is not available" error from Windows Explorer.

Steps to Reproduce

1. Open Claude desktop app on Windows
2. Open the Dispatch panel
3. Click the "output" button on any completed task/session

Expected Behavior

Windows Explorer opens the session's outputs folder.

Actual Behavior

Windows Explorer shows: Location is not available — C:\Users\...\AppData\Roaming\Claude\local-agent-mode-sessions\<sessionId>\outputs is unavailable.

Root Cause (Investigated)

The Claude desktop app is an MSIX-packaged app. Its session data is physically stored at:

C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\local-agent-mode-sessions\

However, C:\Users\<user>\AppData\Roaming\Claude\local-agent-mode-sessions is a junction/symlink pointing to the above package path.

When Dispatch calls explorer.exe with the junction-based path (AppData\Roaming\Claude\...), Windows Explorer cannot traverse junctions that point into the Packages folder — this is a Windows security boundary for MSIX app containers.

Workaround: Opening the direct package path works fine:

C:\Users\<user>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\local-agent-mode-sessions\<sessionId>\outputs

Fix Suggestion

When constructing the path to pass to explorer.exe, Dispatch should resolve the junction and use the real/canonical path (the Packages\...\LocalCache\Roaming path) instead of the virtual AppData\Roaming path.

In PowerShell: (Get-Item $junctionPath).Target resolves the junction target.

Environment

• OS: Windows 11 Home 10.0.26200
• Claude version: Desktop app (MSIX package: Claude_pzs8sxrjxfjjc)