anomalyco / anomalyco/opencode

VS Code extension still not auto-installed on Windows despite TERM_PROGRAM=vscode (recurrence of #36404)

Open
#49,503 0 comments 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Sep 17, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

The VS Code extension (sst-dev.opencode) is not automatically installed when running opencode from the VS Code integrated terminal, even though all documented prerequisites are met. Manual installation via the code CLI works fine.

This is a recurrence of #36404, which was auto-closed after 60 days of inactivity without a fix. Still reproducible on the latest version.

Environment
  • OS: Windows 11
  • OpenCode: 1.18.31
  • Shell: PowerShell 7 (pwsh)
  • VS Code integrated terminal
Verified
  • TERM_PROGRAM is set to vscode:
    PS> echo $env:TERM_PROGRAM
    vscode
    
  • VS Code CLI is on PATH and works (code --install-extension ... succeeds)
  • code --list-extensions shows no extensions before manual install — opencode never attempts to install the extension
  • Running opencode launches the TUI normally but skips extension installation entirely
  • Manual install succeeds:
    PS> code --install-extension sst-dev.opencode
    Extension 'sst-dev.opencode' v0.0.13 was successfully installed.
    
Investigation (from #36404)

packages/opencode/src/ide/index.ts defines ide(), install() and alreadyInstalled(), but Ide.install is never referenced anywhere in packages — only alreadyInstalled() is referenced in its unit tests. The auto-install path appears to be dead code.

OpenCode version

1.18.31

Steps to reproduce
  1. Open VS Code on Windows
  2. Open the integrated terminal (pwsh 7)
  3. Confirm echo $env:TERM_PROGRAM prints vscode
  4. Run opencode
  5. Run code --list-extensionssst-dev.opencode is not installed
Operating System

Windows 11

Terminal

VS Code integrated terminal (pwsh 7)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.