[FEATURE]:The OpenCode extension for VS Code to be used in a Windows environment.

[Dwight2458]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

The OpenCode extension for VS Code cannot be used in a Windows environment.
When launched through the VS Code extension, the opened terminal is the default cmd terminal, not the bash terminal, which causes the 'opencode' command to be unrecognized.

[github-actions]

This issue might be a duplicate of or related to existing Windows environment issues. Please check:

• Windows Support #631: Windows Support (meta issue tracking all Windows problems)
• Bash tool executes bash commands with cmd.exe #4599: Bash tool executes bash commands with cmd.exe (directly related - bash commands fail when cmd.exe is used instead of bash)
• shell mode (!) is broken on Windows Powershell #4671: shell mode (!) is broken on Windows Powershell (shell/terminal issues on Windows)
• Recommended Terminal for Windows - as all I tried have weird artifacts so far #2821: Recommended Terminal for Windows (Windows terminal compatibility issues)
• vscode extension: Some extension keyboard shortcuts don't work (windows) #3393: vscode extension: Some extension keyboard shortcuts don't work (windows) (Windows-specific extension issues)
• [FEATURE]: cleaner and more aware extensions integration with vscode #7275: [FEATURE]: cleaner and more aware extensions integration with vscode (broader VS Code extension integration improvements)

The core issue appears to be that the VS Code extension launches a cmd terminal by default on Windows instead of a bash-compatible shell. This is related to issue #4599 which documents how bash commands fail when cmd.exe is the default shell.

Feel free to ignore if none of these address your specific case.