Bug: workspace creation fails on macOS for paths with spaces (firmlinked APFS volume trailing colon)

[iZiwer]

Problem

On macOS, selecting a workspace folder whose path lives on a firmlinked APFS
volume (an external drive's system/data pair, where the volume name contains
spaces) fails with:

workspace create failed: workspace-invalid-path: cannot create a workspace at
"/Volumes/.../code:/": ENOENT: no such file or directory, realpath '/Volumes/.../code:/'

Root cause

osascript's POSIX path of (choose folder) leaks the HFS : directory
separator into the returned path as a trailing :/ on firmlinked volumes, so
fs.realpath rejects the otherwise-valid directory.

Fix (available in my fork)

One-line normalization in
packages/host/directory-picker-native/src/native-picker.ts strips the trailing
:/ back to /, plus a regression test.

Fork: https://github.com/iZiwer/deepseek-harness
Commit: e147474

[denial123789]

I turned this into a source-pinned operator guide: Fix macOS workspace picker trailing-colon paths.

The key diagnostic distinction is now explicit: spaces in a volume name are valid; the strong discriminator is a colon immediately before the terminating slash in the exact AppleScript output. The guide preserves fs.realpath as the workspace identity contract and keeps the correction at the macOS picker boundary.

It also adds a safe current workflow:

• reproduce POSIX path of selectedFolder directly and preserve the exact output;
• compare only the narrow terminal :/ to / spelling and prove the normalized path with test -d;
• use a direct-path or browse-picker flow when available instead of renaming the volume or editing the registry;
• test an official fix at both layers: adapter semantics, then workspace create/reuse after a cold Host restart.

The proposed commit is linked as external evidence rather than described as released behavior. The official source references remain pinned to 99f6f02 until a reviewed fix lands upstream.

[GideonBature]

Problem

On macOS, selecting a workspace folder whose path lives on a firmlinked APFS volume (an external drive's system/data pair, where the volume name contains spaces) fails with:

workspace create failed: workspace-invalid-path: cannot create a workspace at "/Volumes/.../code:/": ENOENT: no such file or directory, realpath '/Volumes/.../code:/'

Root cause

osascript's POSIX path of (choose folder) leaks the HFS : directory separator into the returned path as a trailing :/ on firmlinked volumes, so fs.realpath rejects the otherwise-valid directory.

Fix (available in my fork)

One-line normalization in packages/host/directory-picker-native/src/native-picker.ts strips the trailing :/ back to /, plus a regression test.

Fork: https://github.com/iZiwer/deepseek-harness Commit: e147474

I am facing the same thing right now and I don't know a way around it, please were you able to find a way around it? @denial123789 @iZiwer