Updater offers in-app updates for Nix store installs; taking it breaks the running session #54022

Activity

1. github-actions

   assigned

   kitlangton

   on Oct 8, 2026
2. opencode-agent commented on Oct 8, 2026

   

   opencode-agentBot

   on Oct 8, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report. I could reproduce the main part of this with a simulated Nix-store install: a released binary in a read-only /nix/store-style directory with no npm manifest, so the updater can't detect how it was installed. I used 2.0.25 so that a newer release would be offered. There's no Nix in my sandbox, so I didn't build the actual flake.

   • /update (and the home-screen hint) still offers the update, with an Update button.
   • Accepting it fails with Installation method not found, and the update stays on offer afterwards.

   In my run the session did not hang: after the error I could close the dialog and keep typing. The hang you saw may depend on something only the real flake build has, such as the wrapProgram wrapper or the real store path. If you can share the log lines around the update attempt (the update / updater entries in the opencode log), that would help pin it down.

   I couldn't run this check from source, because source checkouts skip update checks. But the updater and the Nix packaging are unchanged on the latest v2 (a2e3dd2), so the same behaviour is expected there. The recording and script below show the steps. Your PR #54021 sets OPENCODE_DISABLE_AUTOUPDATE=1 in the flake wrapper, which avoids this for flake installs. #52122 is the same problem in the Nix desktop build.

   recording.mp4

   

   

   Reproduction script (drive.ts)

   // Repro for #54022: in-app update offered for a Nix-store-style install.
   // Setup: put an opencode binary in a read-only /nix/store-like path with no
   // package.json next to it (so Updater.method() returns undefined), first on PATH:
   //   S=/tmp/opencode/nix/store/abc123-opencode-2.0.25/bin; mkdir -p $S
   //   (copy the @opencode/[email protected] binary to $S/opencode); chmod -R a-w $S
   //   export PATH=$S:$PATH
   // 2.0.25 is used so that a newer release (2.0.26+) is offered.
   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, keypressOverlay: true },
     },
     ({ ui }) =>
       Effect.gen(function* () {
         yield* Effect.sleep("6 seconds")
         yield* ui.screenshot("01-home")
         yield* ui.type("/update")
         yield* Effect.sleep("1 second")
         yield* ui.screenshot("02-command")
         yield* ui.enter()
         yield* Effect.sleep("8 seconds")
         yield* ui.screenshot("03-dialog")
         yield* ui.enter()
         yield* Effect.sleep("15 seconds")
         yield* ui.screenshot("04-after-accept")
         yield* ui.press("escape")
         yield* Effect.sleep("2 seconds")
         yield* ui.type("hello still responsive?")
         yield* Effect.sleep("2 seconds")
         yield* ui.screenshot("05-responsive")
       }),
   )

   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.
3. opencode-agent

   added

   reproduced

   on Oct 8, 2026
4. fabiob commented on Oct 22, 2026

   

   fabiob

   on Oct 22, 2026

   ContributorAuthor

   More actions

   Status update, since the fix landed in two pieces:

   • fix(cli): return unavailable in updater.check when install method is unknown #54672 (merged) fixed the failure mode: check()/apply() now report updates as unavailable when no installation method is detected, so accepting an update no longer wedges the session on a Nix store install.
   • fix(nix): disable the self-updater in the flake build #57979 (open) removes the remaining annoyance for flake installs: the flake now sets OPENCODE_DISABLE_AUTOUPDATE=1 in the wrapper, so the automatic update notice no longer appears for installs that can't take it.

   One gap that remains untracked: the desktop client's own updater (electron-updater in packages/gui-extensions/src/updater/) reads neither the variable nor any installation-method detection, so a Nix store install of the desktop app can still be offered an update it cannot apply (see carterworks' note above). A fix there would follow the same shape — detect a store install and report the updater disabled (the state already exists). Happy to file a separate issue for it if useful.