Setting up ProjectShelf on Windows

The presets are already Windows-shaped, so there is less to do here than on other platforms. What is worth knowing is why there are four terminal entries and when each one generates something different.

Why cd is not always cd

Command Prompt will not change drive with a bare cd. Moving from C: to D: needs the /d flag, which is why the Command Prompt entry carries a different directory change prefix from PowerShell. Pick the wrong one and the command silently does nothing.

cd "D:\work\aurora"
cd /d "D:\work\aurora"

Windows Terminal

Windows Terminal can open directly at a folder, so rather than pasting a cd line you can have ProjectShelf generate a command that opens a new tab already in the project.

wt -d "{path}"

Select several projects and you get one line per project, which opens a tab for each. To use a specific profile, add the profile flag before the directory.

wt -p "PowerShell" -d "{path}"

Git Bash and path formats

Git Bash accepts Windows paths in quotes, so the stored path works without conversion. If you prefer the POSIX form, store it that way instead. What matters is that the path you save is the one you want pasted.

cd "D:\work\aurora"
cd /d/work/aurora

Editors

VS Code, Cursor, and WebStorm are configured out of the box. VS Code and Cursor also register a URL scheme, so ProjectShelf can hand the folder straight over and the editor opens without you pasting anything. The command is still copied as a fallback in case the scheme is not registered.

Install it as an app

In Edge or Chrome, use the install icon in the address bar, or the Install app button in the ProjectShelf sidebar. Installed, it gets a Start menu entry, opens in its own window, and works offline.