SHIFT-CMD-C doesn't work in a vscode ssh session.

Discord username (optional)

andr-ec

Describe the bug

If I press SHIFT-CMD-C from a vs code window in a local project it opens that projects directory. But if it's a vscode window for a remote connection, it just opens in my ~/Downloads folder.

To reproduce

1. open a project in vscode that is is a window connected to a remote server (ssh).
2. press SHIFT-CMD-C

Result: a new warp window will open in the ~/Downloads folder

Expected behavior

It should open the correct directory in an ssh session in warp.

Screenshots

No response

Operating system

MacOS

Operating system and version

MacOS Ventura

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Start by reproducing the shortcut behavior in a macOS Ventura VS Code window connected to a remote server over SSH, then compare it with a local project window. Trace how SHIFT-CMD-C determines the project directory and how Warp receives the remote-session context. Done means the shortcut opens the corresponding remote project directory in Warp rather than ~/Downloads, without changing local-project behavior.