[Bug]: Error on second system entry

[suxg001]

Prerequisites

• I have searched existing issues to avoid duplicates
• I am using the latest version of oh-my-opencode
• I have read the documentation

Bug Description

"name": "BunInstallFailedError",
"data": {
"pkg": "oh-my-opencode",
"version": "latest"
}
}

Steps to Reproduce

"name": "BunInstallFailedError",
"data": {
"pkg": "oh-my-opencode",
"version": "latest"
}
}

Expected Behavior

Expected to open and login normally

Actual Behavior

"name": "BunInstallFailedError",
"data": {
"pkg": "oh-my-opencode",
"version": "latest"
}
}

Doctor Output

"name": "BunInstallFailedError",
  "data": {
    "pkg": "oh-my-opencode",
    "version": "latest"
  }
}

Error Logs

Configuration

Additional Context

No response

Operating System

macOS

OpenCode Version

1.1.14

[winsdon]

windows也如此

[CodeWhimsy-Kris]

一样的问题

[WuChaoli]

一样，ubuntu24.04也进不去

[WuChaoli]

可以在命令行：opencode stats，会跳出一个日志
Error: Unexpected error, check log file at /home/ubuntu/.local/share/opencode/log/2026-01-17T034330.log for more details
把这个日志喂给AI看一下是什么问题
我检查出来时因为源检查不到包所有安装错误了，更换掉bun的源就好了

[code-yeongyu]

@sisyphus-dev-ai is our installer sets as @latest by default?

[WuChaoli]

谢谢我已收到喽~我会在第一时间处理，请耐心等等哦。

[sisyphus-dev-ai]

Answer: Plugin Version Behavior

Yes, the installer uses @latest by default — but with intelligent version tagging.

How it Works

The installer uses getPluginNameWithVersion() in src/cli/config-manager.ts (line 137-150):

export async function getPluginNameWithVersion(currentVersion: string): Promise<string> {
  const distTags = await fetchNpmDistTags(PACKAGE_NAME)

  if (distTags) {
    const allTags = new Set([...PRIORITIZED_TAGS, ...Object.keys(distTags)])
    for (const tag of allTags) {
      if (distTags[tag] === currentVersion) {
        return `${PACKAGE_NAME}@${tag}`
      }
    }
  }

  return `${PACKAGE_NAME}@${currentVersion}`
}

Version Resolution Priority

1. @latest — If current version matches npm's latest tag
2. @beta — If current version matches npm's beta tag
3. @next — If current version matches npm's next tag
4. Pinned version (e.g., @3.0.0-beta.2) — If no tag matches

Test Evidence

From config-manager.test.ts:

• "returns @latest when current version matches latest tag" → oh-my-opencode@latest
• "returns @beta when current version matches beta tag" → oh-my-opencode@beta
• "returns pinned version when no tag matches" → oh-my-opencode@3.0.0-beta.2
• "returns pinned version when fetch fails" → Falls back to pinned version on network error

Relation to Issue #716

The users reporting errors on second entry may be affected by:

1. npm registry issues in China — WuChaoli mentioned changing bun's source fixed their issue
2. When fetchNpmDistTags() fails (network error), it falls back to pinned version, which should still work

The version tagging logic itself is robust and handles network failures gracefully.

[zhaozhongwenzzw]

源换成官方源就能解决了

[fastknifes]

我已经安装成功了,并且成功运行了一段时间。 但在某一个时刻再次打开opencode的时就报这个错误

报错日志

 stderr=Resolving dependencies
error: moving "oh-my-opencode-windows-x64" to cache dir failed
EPERM: Operation not permitted (NtSetInformationFile())
  From: .5faede4df7fffbb1-00000001.oh-my-opencode-windows-x64
    To: oh-my-opencode-windows-x64@3.1.3@@@1
Resolved, downloaded and extracted [17]
error: InstallFailed extracting tarball from oh-my-opencode-windows-x64
 done

[luckywbj2025]

所有配置文件给权限就解决了， sudo chmod -R 777 .

[suse-coder]

@sisyphus-dev-ai please fix it urgently