[BUG] /update offers 2.0.7 on pacman-managed install, but upgrade cannot work (method undetected; GitHub release v2.0.7 missing) #49660

Activity

1. github-actions

   assigned

   kommander

   on Sep 18, 2026
2. disonjer

   changed the title [-][BUG] Update prompt offers 2.0.7 to pacman-managed install, but upgrade is impossible (method undetected; GitHub release v2.0.7 missing)[/-] [+][BUG] /update offers 2.0.7 on pacman-managed install, but upgrade cannot work (method undetected; GitHub release v2.0.7 missing)[/+] on Sep 18, 2026
3. aron-intframe commented on Sep 18, 2026

   

   aron-intframe

   on Sep 18, 2026

   More actions

   Confirmed on v2.0.5 source, and one part of the report is narrower than stated: the v2 curl updater does not use GitHub Releases at all, so the missing v2.0.7 release only breaks the legacy opencode.ai/install script (dev branch), not /update.

   What I ran against the v2.0.5 checkout (packages/cli/src/services/updater.ts, updater-action.ts executed as-is, types stripped):

   $ node repro.mjs
   { execPath: '/usr/bin/opencode', isCurl: false, manifest: '/usr/package.json', manifestExists: false, method: undefined }
   { current: '2.0.5', latest: '2.0.7', notify: 'notify', disable: 'none' }
   { current: '2.0.8', latest: '2.0.7', notify: 'notify' }      # no semver-gt guard, as you said
   200 https://registry.npmjs.org/@opencode/cli-linux-x64/-/cli-linux-x64-2.0.7.tgz
   404 https://github.com/anomalyco/opencode/releases/download/v2.0.7/opencode-linux-x64.tar.gz
   

   So the actual sequence for a pacman install:

   1. inspect() -> action("2.0.5","2.0.7","notify") returns notify and the home screen shows the banner. method() is never consulted at this point.
   2. Pressing Update calls apply() -> install() -> method(). method() checks only ~/.opencode/bin/opencode and a package.json two levels above process.execPath. For /usr/bin/opencode that is /usr/package.json, which does not exist, so installedPackage is undefined and method() returns undefined -> "Installation method not found".
   3. Had method() returned curl, upgrade() fetches https://opencode.ai/v2/install, and that script resolves @opencode/[email protected] from registry.npmjs.org (200 above). The GitHub Releases dependency lives only in https://opencode.ai/install, which 307s to raw.githubusercontent.com/.../refs/heads/dev/install and does releases/download/v${version}/... (line 194 of that script). That is the 1.x installer; it cannot install 2.x from GitHub because nothing publishes assets there.

   Workaround until this is fixed: the banner is driven by run(), which honours the policy file, so either

   echo '{"update":"disable"}' > ~/.config/opencode/opencode.json   # or "autoupdate": false
   # or
   export OPENCODE_DISABLE_AUTOUPDATE=1
   

   readPolicy() only reads config.json / opencode.json / opencode.jsonc under $XDG_CONFIG_HOME/opencode (or $OPENCODE_CONFIG_DIR), not a project-level config. A manual /update still goes through check(), which ignores the policy, but it no longer nags.

   Suggested fix in updater.ts: have run() call method() before returning {type:"available"} under notify/auto, and return undefined (with the existing "installation method not found" log) when it is undetected. That drops the banner for distro packages without touching the manual /update path. Detecting the package manager itself (pacman -Qo "$(realpath "$0")", dpkg -S, brew --prefix) would be a separate, nice-to-have step so the dialog can say "update via your package manager".
4. Acidburn0x90 commented on Oct 25, 2026

   

   Acidburn0x90

   on Oct 25, 2026

   More actions

   Same failure on 2.1.3 with the Arch extra package, so it survived 2.0.5 → 2.1.3:

   $ opencode --version && pacman -Q opencode
   opencode v2.1.3
   opencode 2.1.3-1
   
   $ pacman -Qo "$(readlink -f "$(command -v opencode)")"
   /usr/bin/opencode is owned by opencode 2.1.3-1
   
   $ opencode upgrade
   ■  Could not detect the installation method. Pass --method to choose how to upgrade OpenCode.
   
   $ opencode upgrade --method pacman
   ERROR  Invalid value for flag --method: "pacman". Expected: "curl" | "npm" | "pnpm" | "bun" | "yarn" | "vp" | "brew" | "winget"
   

   packages/cli/src/services/updater.ts on dev is unchanged on this point:

   export const methods = ["curl", "npm", "pnpm", "bun", "yarn", "vp", "brew", "winget"] as const

   and method() still bails at if (!installedPackage) return before any package-manager probe, so a distro binary at /usr/bin/opencode can never be identified.

   Two notes for whoever picks this up:

   • pacman -Qo <realpath(process.execPath)> returns ownership and the installed version in one call (/usr/bin/opencode is owned by opencode 2.1.3-1), and pacman -Si opencode with LC_ALL=C gives the sync-db candidate. dpkg -S / rpm -qf are the equivalents for the other distro packages.
   • The upgrade itself needs root, and the TUI's child process has no controlling terminal, so sudo pacman -Syu cannot authenticate from there. Detection plus "update via your package manager, then restart" is probably the realistic scope; feat(desktop): honor OPENCODE_DISABLE_AUTOUPDATE in the updater #55155 and fix(nix): disable the self-updater in the flake build #57979 already take that direction for the env-var and nix cases.

   Workaround in use here: a custom ~/.config/opencode/commands/update.md that overrides /update with a helper that picks repo vs AUR (pacman -Qm) and runs sudo pacman -S --needed opencode or yay -S opencode.
5. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed report. I could reproduce the main problem.

   To simulate a distro-package install, I copied the @opencode/cli release binary into a plain directory on PATH and removed the bun global install, so no package manager owns it. Then:

   • The home screen shows /update to install v2.2.0.
   • /update opens the "Update available" dialog with Skip / Update.
   • Pressing Update fails with "Could not detect the installation method. Update with your package manager or download the latest release."

   I ran this on 2.1.4, not 2.0.5: the drive tooling can't run 2.0.5, and a release has to be older than the current latest (2.2.0) to be offered an update. The code that decides when to show the prompt is the same on the latest dev (950111f). The update check behind the home-screen hint still doesn't look at the install method; only the dialog's install step does. The recording and screenshots below show the whole flow, and the script below reproduces it.

   On your second point: v2.0.7 still has no binary assets, but current v2 releases do. For example, releases/download/v2.2.0/opencode-linux-x64.tar.gz now resolves. So the GitHub Releases part looks addressed for newer versions.

   Related issues:

   • Updater offers in-app updates for Nix store installs; taking it breaks the running session #54022: the same unwanted update offer for Nix store installs
   • [v2] cli: update prompt recommends older version #47714: an update is offered whenever the version differs, even when it isn't newer

   recording.mp4

   

   

   Reproduction script (drive.ts)

   // Reproduces #49660: on an install not managed by curl/npm/bun/... (e.g. a pacman package
   // binary in /usr/bin), the TUI still advertises an update, and /update cannot perform it.
   // Setup (simulates a distro-package binary; drive runs `opencode2` from PATH):
   //   bun add -g @opencode/[email protected]   # any release older than the current latest
   //   mkdir -p /opt/usrbin && cp ~/.bun/install/global/node_modules/@opencode/cli/bin/opencode.exe /opt/usrbin/opencode2
   //   bun remove -g @opencode/cli      # so no package manager owns it
   //   PATH=/opt/usrbin:$PATH opencode-drive run drive.ts
   import { Effect } from "effect"
   import { OpenCodeDriver } from "opencode-drive"
   
   export default OpenCodeDriver.use(
     { ...(process.env.OC_DEV ? { opencode: { dev: process.env.OC_DEV } } : {}), tui: { recording: true } },
     ({ ui }) =>
       Effect.gen(function* () {
         yield* ui.waitFor("/update", { timeout: 60000 })
         yield* ui.screenshot("home-update-hint")
         yield* ui.type("/update")
         yield* Effect.sleep("1 second")
         yield* ui.enter()
         yield* Effect.sleep("4 seconds")
         yield* ui.screenshot("update-dialog")
         yield* ui.enter()
         yield* Effect.sleep("6 seconds")
         yield* ui.screenshot("after-update")
       }),
   )

   Run it with opencode-drive: opencode-drive run ./drive.ts. It drives opencode from your PATH; set OC_DEV to the path of an OpenCode checkout to run that from source instead.
6. opencodejr

   added

   reproduced

   on Oct 28, 2026