Repository navigation
cli: support updating Scoop opencode2 installations #52822
Description
Description
OpenCode V2 cannot update a CLI installed from Scoop's versions bucket. The V2 updater does not include Scoop among its recognized installation methods, so opencode update cannot associate the running opencode2 executable with Scoop and does not run scoop update opencode2.
The Scoop opencode2 manifest installs the platform executable at ~\scoop\apps\opencode2\current\opencode.exe. Scoop itself correctly reports an available update, but the built-in updater requires a separate manual command.
Plugins
None
OpenCode version
2.0.20
Steps to reproduce
- Run
scoop bucket add versions. - Install V2 with
scoop install opencode2. - When an update is available, run
opencode updateor accept the TUI update action. - Observe that OpenCode cannot detect the installation method instead of updating the
opencode2Scoop app. - Confirm that
scoop statuslists the update andscoop update opencode2applies it.
Screenshot and/or share link
No response
Operating System
Windows 11
Terminal
PowerShell
Activity
github-actions commentedon Oct 2, 2026
This issue might be a duplicate of existing issues. Please check:
opencodejr commentedon Oct 27, 2026
Thanks for the detailed report, @maharshi365!
This is a request to have the V2 updater recognise Scoop installs (the
opencode2app from theversionsbucket). With that,opencode updateand the TUI update action would runscoop update opencode2for you.Right now the V2 updater only detects the OpenCode installer (curl), npm, pnpm, Bun, Yarn, vp, Homebrew and WinGet. Scoop isn't one of the supported update methods yet, so the behaviour you saw is expected for now and not a bug. I've marked this as a feature request for the maintainers to consider.
Until then, running
scoop update opencode2directly, as you already do, is the way to update.