cli: upgrade reports success but the running binary is not replaced when another copy is registered with the package manager #52152

Activity

1. github-actions

   assigned

   neriousy

   on Sep 29, 2026
2. github-actions commented on Sep 29, 2026

   

   github-actionsBot

   on Sep 29, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • opencode upgrade reports success but version remains unchanged #15248: opencode upgrade reports success but the version remains unchanged.
   • opencode upgrade not upgrading (brew) #11021: the upgrade reports completion, but the running Homebrew version does not change.
   • cli: upgrade --method bun reports success on Windows but leaves the old binary in place #51386: upgrade --method bun reports success while the old binary remains in place.
3. coygeek commented on Oct 3, 2026

   

   coygeek

   on Oct 3, 2026

   More actions

   Also reproduced on OpenCode 2.0.22, macOS arm64, with npm 12.0.2 and Node.js v22.23.2.

   In this case, @opencode/cli is installed globally in a custom npm prefix, and npm’s default global prefix does not contain the package. Running opencode2 update 2.0.22 exits with code 1:

   Could not detect the installation method. Pass --method to choose how to upgrade OpenCode.
   

   The same failure occurred on 2.0.18. Installing 2.0.22 manually with npm and the original explicit --prefix succeeded, but the built-in updater still fails afterward.

   This appears to be another symptom of the prefix-selection problem described here. A fix should cover both layouts: a custom-prefix installation with no default-prefix copy, and a custom-prefix installation alongside a default-prefix copy.
4. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed report. I was able to reproduce this.

   Setup: @opencode/[email protected] installed with npm install -g (default prefix /usr/local), and @opencode/[email protected] with npm install -g --prefix ~/.local, with ~/.local/bin first on PATH. Running opencode upgrade 2.0.17 printed Using method: npm and Upgrade complete and exited 0. Afterwards the running copy was still v2.0.19, and the default-prefix copy had changed to v2.0.17.

   The same thing happens with the latest release, 2.2.0 (2.0.16 global, upgrading to 2.1.4). On the latest dev (86ce19d), the code that detects the install method and runs the upgrade is unchanged from 2.2.0. The script below reproduces it.

   Related: your PR #52149, which takes the approach of only using a package manager whose global root contains the running binary.

   Reproduction script (repro.sh)

   #!/usr/bin/env bash
   # Reproduces #52152: `opencode upgrade` upgrades a different npm-global copy, not the running binary.
   # Usage: RUNNING=2.0.19 OTHER=2.0.16 TARGET=2.0.17 bash repro.sh
   set -u
   RUNNING=${RUNNING:-2.0.19}; OTHER=${OTHER:-2.0.16}; TARGET=${TARGET:-2.0.17}
   PREFIX=${PREFIX:-$HOME/.local}
   npm install -g "@opencode/cli@$OTHER" >/dev/null 2>&1                      # copy in the default global prefix
   npm install -g --prefix "$PREFIX" "@opencode/cli@$RUNNING" >/dev/null 2>&1   # copy in a custom prefix
   DEFAULT_BIN="$(npm config get prefix)/bin/opencode"
   export PATH="$PREFIX/bin:$PATH"                                               # custom-prefix copy first on PATH
   echo "BEFORE: running=$(opencode --version) ($(command -v opencode))  npm-global=$($DEFAULT_BIN --version)"
   opencode upgrade "$TARGET" </dev/null 2>&1 | sed 's/\x1b\[[0-9;?]*[A-Za-z]//g' | grep -E 'method|From|complete|failed|Done'
   echo "exit=${PIPESTATUS[0]}"
   echo "AFTER : running=$(opencode --version)  npm-global=$($DEFAULT_BIN --version)"

   Run it: bash repro.sh
5. opencodejr

   added

   reproduced

   on Oct 28, 2026
6. rekram1-node

   closed this as completedin #63152on Nov 11, 2026