Cross platform open opencode in VSCode #1465

Closed
opened 2026-02-16 17:31:07 -05:00 by yindo · 5 comments
Owner

Originally created by @eugenkleinschmidt on GitHub (Aug 24, 2025).

Originally assigned to: @fwang on GitHub.

On windows cmd/powershell this is not working
https://github.com/sst/opencode/blob/0fd312346bc172782ea7e45160deb8851d894dbc/sdks/vscode/src/extension.ts#L60

Originally created by @eugenkleinschmidt on GitHub (Aug 24, 2025). Originally assigned to: @fwang on GitHub. On windows cmd/powershell this is not working https://github.com/sst/opencode/blob/0fd312346bc172782ea7e45160deb8851d894dbc/sdks/vscode/src/extension.ts#L60
yindo closed this issue 2026-02-16 17:31:07 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 24, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #1372: Enable choosing which shell is used by opencode VS Code extension - specifically mentions Windows PowerShell compatibility issues with the VSCode extension
  • #631: Windows Support - umbrella issue tracking all Windows-related problems
  • #413: Editor Open Error in Windows - mentions editor-related issues on Windows platform

The issue you're reporting about line 60 in extension.ts (terminal command execution) appears to be closely related to #1372, which discusses the exact same problem with PowerShell not recognizing the variable setting syntax used in the VSCode extension.

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

@github-actions[bot] commented on GitHub (Aug 24, 2025): This issue might be a duplicate of existing issues. Please check: - #1372: Enable choosing which shell is used by opencode VS Code extension - specifically mentions Windows PowerShell compatibility issues with the VSCode extension - #631: Windows Support - umbrella issue tracking all Windows-related problems - #413: Editor Open Error in Windows - mentions editor-related issues on Windows platform The issue you're reporting about line 60 in extension.ts (terminal command execution) appears to be closely related to #1372, which discusses the exact same problem with PowerShell not recognizing the variable setting syntax used in the VSCode extension. Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Oct 21, 2025):

I think this was fixed by linked pr

@rekram1-node commented on GitHub (Oct 21, 2025): I think this was fixed by linked pr
Author
Owner

@nickwang0808 commented on GitHub (Oct 22, 2025):

The fix is not deployed yet to vscode market place

@nickwang0808 commented on GitHub (Oct 22, 2025): The fix is not deployed yet to vscode market place
Author
Owner

@rekram1-node commented on GitHub (Oct 22, 2025):

Ah sorry about that, ill release it then

@rekram1-node commented on GitHub (Oct 22, 2025): Ah sorry about that, ill release it then
Author
Owner

@rekram1-node commented on GitHub (Oct 22, 2025):

@nickwang0808 just released 0.0.12: https://marketplace.visualstudio.com/items?itemName=sst-dev.opencode#review-details

@rekram1-node commented on GitHub (Oct 22, 2025): @nickwang0808 just released 0.0.12: https://marketplace.visualstudio.com/items?itemName=sst-dev.opencode#review-details
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1465