Continue Agent filesystem tools resolve `C:\workspace` instead of Remote-SSH workspace

[anomaly0617]

Before submitting your bug report

• I've tried finding an answer on the Continue docs site
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

* Windows 11
* VS Code
* Continue 2.1.0 pre-release (also tried with 2.0.0 release version)
* Remote-SSH
* Debian (remote)
* Workspace opened at `/opt`
* Repository located at `/opt/billing`
* Ollama remote backend

**Expected**

Filesystem tool reports:


/opt


or


/opt/billing


depending on the active workspace.

**Actual**

Filesystem tool attempts to access:


C:\workspace


and returns:


The directory c:\workspace does not exist.


**Comparison**

OpenAI Codex extension, in the same VS Code window and same Remote-SSH session, correctly reports:


/opt


This strongly suggests the issue is isolated to Continue's workspace resolution for Agent filesystem tools.

Description

No response

To reproduce

No response

Log output

[bunnysayzz]

👋 Just opened a PR that fixes this: #13096

Root cause found: the agent/plan system message tells models to use filesystem tools with paths "relative to the root of the workspace" — but never tells the model what that root actually is. On local workspaces the model can infer it from file:// context URIs; on Remote-SSH the workspace is a vscode-remote://ssh-remote+host/opt URI, so the real path is never visible and the model ends up guessing (e.g. C:\workspace).

The fix: resolve the workspace root from the workspace URI (getWorkspaceDisplayPath() handles file://, vscode-remote://, vscode-vfs://, and skips unsupported schemes) and inject it into the agent/plan system message as a <workspace_info> block whenever tools are enabled. Covered by unit tests for the path conversion and the injection behavior.

Would appreciate a review when you get a chance 🙏