Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I believe this is a bug. I'll try to join the Continue Discord for questions
• 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

- OS: Windows 11
- Continue version: 1.2.7
- IDE version: 1.104.3
- Model: N/A
- config: N/A

Description

When working in .devcontainers continue.dev cannot run commands in the terminal

Attempt to run results in error

run_terminal_command failed with the message: The URL must be of scheme file

Please try something else or request further instructions.

Running commands in the terminal does work with the native Gitub Copilot extension so there must be some detection mechanism the extension can perform to know which URL scheme to use.

From my limited understanding VSCode uses URI schemes to represent resources in different contexts.

file:// - Local file system paths
vscode-remote:// - Files inside remote environments (containers, SSH, WSL)

It seems continue.dev is hard-coded or not adapting to the environment it is running in and always using file:// when it should be using vscode-remote://
Although the error message "The URL must be of scheme file" makes it seem like it should be file:// but this may be misleading.

This issue might become part of #928

To reproduce

1. Open Agent Chat
2. Enter prompt which causes continue.dev to suggest running command in terminal
3. Click "Run"

Expected:
Command executes successfully

Actual:
Error response

Log output