Skip to content

[Windows] Startup opens several PowerShell windows: pnpm/npm/vp 'list -g' version checks run visibly #62837

Closed as duplicate

Description

@maxiusofmaximus

Summary

On Windows, starting opencode opens several PowerShell console windows. Each one is a package-manager version check that runs at startup. Visible windows for a background check are a bad experience. By default there should be no visible window at all. If a check really must run, it should run hidden, and the UI should show the status (for example "checking for updates…") and then reset.

Environment

  • opencode 2.2.6 (@opencode/cli), installed globally with pnpm v11
  • Windows 11 Pro 10.0.26300
  • pnpm, npm and vp are installed on the PATH; on this machine they are .ps1 shims

Steps to reproduce

  1. Install opencode globally with pnpm on Windows.
  2. Open a terminal and run opencode.
  3. Several PowerShell windows open and close during startup.

What the log shows

opencode.log has these entries at every startup (role cli):

spawning process command=pnpm args=["list","-g","--depth=0","@opencode/cli"]
spawning process command=npm  args=["list","-g","--depth=0","@opencode/cli"]
spawning process command=vp   args=["list","-g","--json","@opencode/cli"]

The log contains about 6,000 of these list -g spawns across my sessions. Because pnpm and npm are .ps1 scripts on Windows, each spawn opens a visible console window.

Workaround that confirmed the cause

Setting "autoupdate": false in the global config (~/.config/opencode/opencode.json) stops the check. After that change, opening opencode no longer opens the extra windows.

Expected behavior

  • No visible console windows during startup, by default.
  • If the version check has to run, run it without a window (windowsHide or a detached, hidden process) and show the status in the UI, then clear it when it finishes.
  • Consider running only one check per startup, not three, and only when autoupdate is enabled.

Activity

  1. opencodejr commented on Nov 9, 2026

    @opencodejr
    Contributor

    Thanks for the detailed report and for finding the autoupdate: false workaround.

    I think this is a duplicate of #56704. That report has a process trace from a Windows startup showing the same npm list -g --depth=0 @opencode/cli and pnpm list -g ... update checks each opening their own console window, and it asks for these checks to run without a visible window.

    Possible duplicates and related issues, ordered by likelihood:

    Your notes about the vp check, the autoupdate: false workaround and showing the check's status in the UI would be useful on #56704.

    The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.

  2. opencodejr commented on Nov 10, 2026

    @opencodejr
    Contributor

    Closing this as a duplicate of #56704. There's been no reply in the last day saying how this is different. #56704 reports the same thing: on Windows, the startup update checks (npm list -g / pnpm list -g --depth=0 @opencode/cli) each open a visible console window. Please follow that issue for updates. Your extra details would be useful there: the vp check, the "autoupdate": false workaround, and the idea of showing the check's status in the UI. Thanks again for the clear report! If your problem turns out to be different, reply here and we can reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions