[PR #2230] Fix: Set OPENCODE_CALLER env in a more portable way for vscode extension #10241

Closed
opened 2026-02-16 18:14:51 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/anomalyco/opencode/pull/2230

State: closed
Merged: Yes


Currently it is not possible to launch opencode through the vscode extension on windows due to the following error:

OPENCODE_CALLER=vscode: The term 'OPENCODE_CALLER=vscode' is not recognized as a name of a cmdlet, function, script file, or executable program.

This is due to OPENCODE_CALLER being set in a way that is not support neither by powershell nor cmd. We can take advantage of vscode api to set it regardless of the what shell will be used.

#2220

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/2230 **State:** closed **Merged:** Yes --- Currently it is not possible to launch opencode through the vscode extension on windows due to the following error: ```pwsh OPENCODE_CALLER=vscode: The term 'OPENCODE_CALLER=vscode' is not recognized as a name of a cmdlet, function, script file, or executable program. ``` This is due to OPENCODE_CALLER being set in a way that is not support neither by powershell nor cmd. We can take advantage of vscode api to set it regardless of the what shell will be used. #2220
yindo added the pull-request label 2026-02-16 18:14:51 -05:00
yindo closed this issue 2026-02-16 18:14:51 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#10241