anomalyco / anomalyco/opencode

[v2] cli: update prompt recommends older version

Open
#47,714 2 comments 0 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Sep 7, 2026.

2.0
Dominant language
TypeScript
Stars
209k
Forks
27.5k
Avg merge
7h 2m
Merged PRs (30d)
384

Description

Description

Summary

Launching opencode2 version v0.0.0-beta-19215 shows an update prompt recommending v0.0.0-beta-19213, which is older than the currently installed version.

Environment

  • opencode version: opencode2 v0.0.0-beta-19215
  • OS: Windows 11, build 10.0.26200.9278
  • Terminal: Windows Terminal Preview 1.25.1912.0
  • Shell: "Custom pwsh"
Custom pwsh configuration

pwsh.cmd

@echo off
"%LOCALAPPDATA%\Microsoft\WindowsApps\pwsh.exe" -NoLogo -NoProfile -ExecutionPolicy Bypass -File "%~dp0pwsh-wrapper.ps1" %*

pwsh-wrapper.ps1

$realPwsh = '%LOCALAPPDATA%\Local\Microsoft\WindowsApps\pwsh.exe'

$filteredArgs = foreach ($arg in $args) {
	if ($arg -ine '-NoProfile') {
		$arg
	}
}

& $realPwsh @filteredArgs
exit $LASTEXITCODE
  • Install/channel: Beta
  • Active plugins: None configured; no local plugin files found

Reproduction

  1. Install or run opencode2 v0.0.0-beta-19215.
  2. Launch opencode2.
  3. Observe the update notification recommending v0.0.0-beta-19213.

Expected Behavior

The update check should recognize that v0.0.0-beta-19215 is newer than v0.0.0-beta-19213 and should only recommend an update when a newer version is available.

Actual Behavior

The update prompt recommends updating from v0.0.0-beta-19215 to the older version v0.0.0-beta-19213.

Additional Context

This was observed immediately after launching opencode2.

The exact update prompt text has not yet been captured, and it is currently unclear whether the prompt appears on every launch.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.