Bash tool `start` silently fails with Unicode/Arabic filenames on Windows

Environment

• OS: Windows 11 Pro
• Claude Code: v2.1.87
• Interface: VS Code extension

Steps to Reproduce

1. Have a file with Arabic/Unicode characters in the path (e.g. C:\Users\test\مستند.docx)
2. Use the Bash tool: start "" "C:\Users\test\مستند.docx"
3. Command exits with code 0 — no error message
4. File does NOT open

Expected Behavior

File opens in the default application.

Actual Behavior

Silent failure — exit code 0, no error output, file never opens.

Workaround

Use the PowerShell tool with Start-Process instead:

Start-Process "C:\Users\test\مستند.docx"

This works correctly with Unicode/Arabic paths.

Notes

• Affects all file types (.docx, .pdf, .xlsx, etc.)
• Only occurs when the file path contains non-ASCII characters (Arabic, CJK, etc.)
• The Bash start command appears to silently drop Unicode characters in the path