No way to pin a new Claude Code session to a specific root folder in a multi-root VSCode workspace

In a multi-root VSCode workspace (multiple project folders as sibling roots, e.g. covenant/underwriting/ticketing/cortex/deposit-intelligence under one workspace), there is no documented or discoverable way to create a new Claude Code session/tab pinned to a specific root folder as its primary working directory.

• Command Palette → Claude Code: Open in New Tab/Window and the Spark icon entry points don't take a folder parameter.
• An existing session's primary working directory is fixed at creation and cannot be durably changed mid-session — a cd in one Bash tool call does not persist to the next tool call, reverting silently to the original primary directory.
• This means a user has no reliable way to confirm, from the UI alone, which folder a given session/tab is actually scoped to — a tab's title label can visually suggest one folder while the session's real working directory is a different sibling root, with no warning.
• This is worse over Remote-SSH (tested against a VM workspace, [SSH: <host>] in the title bar) where there's an extra layer between the VSCode UI and the actual session state — untested whether this differs from local multi-root workspaces, but worth calling out.

Expected: A documented, reliable way to scope a new session to a chosen root folder (e.g. a right-click "Open Claude Code Session Here" on a folder in the Explorer, or a folder picker when starting a new tab), and/or a persistent, visible indicator of a session's actual live working directory that can't silently drift from what the tab label implies.

Workaround found: Opening a separate single-folder VSCode window per project is the only way to guarantee correct scoping, which defeats the purpose of using a multi-root workspace at all.