Describe the bug
When opening the CLI in a symlink folder on WSL Linux (Ubuntu 24.04), the current folder is reported as the canonical (symlink target) folder instead of the logical path (symlink folder). This breaks workflows that rely on the symlinked path.
Affected version
No response
Steps to reproduce the behavior
- Create a symlinked folder:
ln -s /real/path /symlinked/path
- Enter the symlinked path:
cd /symlinked/path
- Open the CLI in this folder.
- Observe that the folder reported by the CLI is
/real/path instead of /symlinked/path.
Expected behavior
The CLI should report the logical (symlink) path (/symlinked/path) as the current directory, matching user expectation and shell behavior.
Additional context
- Operating system: WSL Linux (Ubuntu 24.04)
- This impacts scripts and tools that depend on the reported path being identical to the logical location.
- Workaround: none known.
Describe the bug
When opening the CLI in a symlink folder on WSL Linux (Ubuntu 24.04), the current folder is reported as the canonical (symlink target) folder instead of the logical path (symlink folder). This breaks workflows that rely on the symlinked path.
Affected version
No response
Steps to reproduce the behavior
ln -s /real/path /symlinked/pathcd /symlinked/path/real/pathinstead of/symlinked/path.Expected behavior
The CLI should report the logical (symlink) path (
/symlinked/path) as the current directory, matching user expectation and shell behavior.Additional context