anomalyco / anomalyco/opencode

Windows: background dependency install failed - @opencode-ai/plugin@local not found

Open
#40,639 1 comment 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 5, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Bug 描述

opencode desktop Windows 版啟動時,反覆出現以下 WARN:

background dependency install failed dir=\"C:\\Users\\User\\.config\\opencode\" error=\"@opencode-ai/plugin: No matching version found for @opencode-ai/plugin@local.\"

此錯誤導致 ~/.config/opencode/ 目錄下所有 Plugin 無法載入(包含本地 Plugin 與 npm Plugin,如 opencode-btw、opencode-readseek 等)。

環境
  • OS: Windows 11
  • opencode: Desktop 版(AppData\Local\Programs@opencode-aidesktop)
  • Shell: pwsh (PowerShell 7)
  • Bun: C:\Users\User.bun\bin\bun.exe(獨立安裝)
重現步驟
  1. 安裝 opencode desktop Windows 版
  2. 設定 ~/.config/opencode/opencode.jsonc,加入任何 npm Plugin(例如 "plugin": ["opencode-btw@latest"])
  3. 重啟 opencode desktop
  4. 查看 ~/.local/share/opencode/log/opencode.log
Log 截取

timestamp=2026-08-05T01:32:26.653Z level=WARN run=03c34ea5 message=\"background dependency install failed\" dir=\"C:\\Users\\User\\.config\\opencode\" error=\"Cause([Fail(NpmInstallFailedError (cause: @opencode-ai/plugin: No matching version found for @opencode-ai/plugin@local.))])\" timestamp=2026-08-05T12:04:17.265Z level=WARN run=23e416fb message=\"background dependency install failed\" dir=\"C:\\Users\\User\\.config\\opencode\" error=\"Cause([Fail(NpmInstallFailedError (cause: @opencode-ai/plugin: No matching version found for @opencode-ai/plugin@local.))])\"

此錯誤在沒有任何本地 Plugin 檔案的情況下仍會發生(plugins/ 目錄為空甚至不存在時)。

影響
  • 所有 npm Plugin 無法載入(/btw、
    eadseek、subagent-statusline 等皆失效)
  • init count 始終為 46,不因 Plugin 增減而改變
  • Plugin 相關的 hook 和 command 完全未註冊
備註

@opencode-ai/plugin 在 npm 上是存在的(目前版本 1.18.13),但 opencode 似乎嘗試以 @local 後綴去解析,導致安裝失敗。

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.