Skip to content

cli: opencode plugin add/check fails for package TUI plugins on Windows - unable to resolve dependency tree #59222

New issue
New issue
Open
Open
cli: opencode plugin add/check fails for package TUI plugins on Windows - unable to resolve dependency tree#59222
Labels
pending closetriaging

Description

@jgarrone82
jgarrone82
opened on Oct 26, 2026

Summary

opencode plugin add, plugin check, and plugin update consistently fail on Windows for package-based TUI plugins with NpmInstallFailedError. add fails with cause Error: unable to resolve dependency tree; check fails with cause Error: Package is not installed. The failure is independent of the user's dependency tree (it reproduces with an empty package.json), while system npm resolves and installs the same packages without issues. As a result, package TUI plugins never load in 2.1.4 and every client start logs plugin operation failed ... NpmInstallFailedError ... stage=prepare.

Environment

  • opencode version: 2.1.4 (channel latest, installed via npm global @opencode/cli)
  • OS: Windows 10.0.26300 (win32 x64)
  • Terminal: Unavailable (headless shell context; reproduced both from an interactive terminal and non-interactively)
  • Shell: PowerShell 7 (pwsh)
  • Install/channel: latest
  • Active plugins: 4 local V2 server plugins (load and work correctly), 1 local TUI plugin loaded by file path, plus the 2 failing package plugins (opencode-subagent-statusline, opencode-sdd-engram-manage)

Reproduction

  1. On Windows with opencode 2.1.4, run:

    opencode plugin add opencode-sdd-engram-manage

    Also reproduces with opencode-subagent-statusline, and with a pinned old version ([email protected]) that worked under V1.

  2. Observe the failure:

    NpmInstallFailedError
    at Npm.reify (...)
    at Npm.add (...)
{
  [cause]: Error: unable to resolve dependency tree
}

  3. Replace ~/.config/opencode/package.json with { "dependencies": {} } and retry → same failure. (Tested with backup/restore of the original file.) This rules out a broken user dependency tree as the cause.

  4. Run opencode plugin check → both packages report (check failed) with cause Error: Package is not installed: <pkg>.

  5. In the same directory, system npm works fine: npm view <pkg> version and npm install both succeed against registry.npmjs.org (no proxy configured, registry reachable).

Expected Behavior

opencode plugin add <pkg> installs the package into opencode's internal plugin cache and registers it in the global configuration; plugin check reports update availability for installed package plugins.

Actual Behavior

  • add/check/update always fail with NpmInstallFailedError.
  • The internal per-package install roots under ~/.cache/opencode/npm/<pkg>@<spec>/ exist but remain empty (the populated cache under ~/.cache/opencode/packages/ dates from before the V2 upgrade and is no longer recognized — hence "Package is not installed" on check).
  • opencode plugin list does not list the package plugins at all: they never load.
  • Every client start logs repeated reconciliation failures: plugin operation failed ... error=NpmInstallFailedError ... stage=prepare ... install=true.

Additional Context

  • The peer dependency ranges of both packages are satisfiable by what is installed, so this does not look like an unsolvable peer conflict:
    • [email protected] peers: @opencode-ai/plugin >=1.17.11 (satisfied by the installed @opencode-ai/plugin 1.18.15), solid-js 1.9.12, @opentui/*.
    • [email protected] peers: @opencode/plugin >=2.0.0 <3 (satisfied after installing @opencode/[email protected]), solid-js, @opentui/*.
    • The failure predates installing @opencode/[email protected] and persists after it.
  • The stack traces point at the bundled Bun-based installer (B:/~BUN/root/..., Npm.reify, Npm.check, Npm.add), so the resolution failure happens inside opencode's embedded package manager, not the system npm.
  • This worked under OpenCode V1 (the populated ~/.cache/opencode/packages/ entries are from before the upgrade); it has been broken since upgrading to V2 2.1.4.
  • Workaround attempted: installing the packages manually with system npm into ~/.config/opencode/node_modules — the packages are present there, but the internal manager still does not recognize them ("Package is not installed"), and plugin add still fails.

Activity

  1. opencode-agent commented on Oct 26, 2026

    @opencode-agent
    opencode-agentBot
    on Oct 26, 2026 – with OpenCode Agent
    Contributor

    Thanks for the detailed report! I think this is a duplicate of #50080. It covers the same package (opencode-sdd-engram-manage) failing the same way: plugin add/update fails in Npm.reify with unable to resolve dependency tree, startup reconciliation logs NpmInstallFailedError at stage=prepare on every launch, the ~/.cache/opencode/npm/<pkg>@<spec> folder stays empty, and system npm installs the package fine. Comments there confirm it on Windows with 2.0.30, 2.1.1 and 2.1.2.

    Possible duplicates and related issues, ordered by likelihood:

    In #50080, the reported workaround is to pin an exact version, e.g. opencode plugin add [email protected], or "[email protected]" in cli.json. You mention that a pinned [email protected] also failed. If pinning [email protected] (or [email protected]) fails for you too, please reply with the output, because that would point to a different problem. Otherwise, a short comment on #50080 saying it still happens on 2.1.4 on Windows would help.

    The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.

  2. opencode-agent
    added
    pending close
    triaging
    on Oct 26, 2026

  3. jgarrone82 commented on Oct 26, 2026

    @jgarrone82
    jgarrone82
    on Oct 26, 2026
    Author

    Tested on 2.1.4 / Windows 11, exactly as suggested, with exact pins on our ~/.config/opencode:

    • opencode plugin add [email protected] → exit 0, installs fine ("installed and added to cli.json").
    • opencode plugin add [email protected] → exit 1, same NpmInstallFailedError from Npm.reify with cause unable to resolve dependency tree.

    So this is not fully covered by the exact-pin workaround in #50080: with an exact pin it still fails when the peer tree cannot be resolved. The discriminator between these two packages:

    • [email protected] peers on @opentui/core and @opentui/solid with ">=0.5.0 <0.7", but this config has @opentui/core/@opentui/solid 0.4.5 pinned (kept for other TUI plugins, which is why it was installed with npm install --force in the first place).
    • [email protected] accepts "@opentui/*": ">=0.4.2 <1", so 0.4.5 satisfies it and reify succeeds.

    Looks like the Bun reify in 2.1.4 fails the whole install when a peer dependency cannot be satisfied by the versions already in the config's node_modules, instead of re-allocating the peer. Happy to test a @opentui bump if that helps isolate it.

  4. jgarrone82 commented on Oct 26, 2026

    @jgarrone82
    jgarrone82
    on Oct 26, 2026
    Author

    Follow-up with concrete differentiating evidence on 2.1.4 / Windows 11:

    • Exact pins fail too for this package, so the tag-spec-only theory from plugin install: TUI plugin fails with empty NpmInstallFailedError — resolver rejects a spec npm installs fine #50080 does not cover everything here:
      • opencode plugin add [email protected] → exit 1, same NpmInstallFailedError / unable to resolve dependency tree at Npm.reify.
      • opencode plugin add [email protected] → exit 1, same failure, on a config where its peers (@opencode-ai/plugin 1.18.15, @opentui/*) were all satisfied.
      • Control: opencode plugin add [email protected] → exit 0, both before and after any config changes.
    • Not the config:
      • Removed a stale opencode-subagent-statusline: ^1.3.0 dep from package.json → still fails.
      • Bumped @opentui/core/@opentui/solid 0.4.5 → 0.5.17 → still fails, then rolled back.
    • Not the resolver stack either, standalone:
      • plain bun install with the same package.json → OK (until consideration: opencode's Npm.reify uses @npmcli/arborist inside the compiled binary).
      • standalone @npmcli/arborist reify({add:[pkg]}, audit:false, ignoreScripts:true, binLinks:true, save:true) in a fresh staging dir with default config → OK for both packages.
    • Workaround (state shaping, no upstream fix needed): built the package tree manually with plain bun install in a scratch dir and pre-seeded an opencode cache generation at ~/.cache/opencode/npm/[email protected]/<epoch-ms>/node_modules. After that, opencode plugin add [email protected] short-circuits the broken reify (active generation exists → metadata) and succeeds; on v2.1.4 the server loads the plugin from dist/server.js and reconciliation completes with 14 plugins and no errors.

    So on 2.1.4 the failure looks package-specific inside OpenCode's arborist call (engram-manage vs statusline differ in the reify outcome under identical config/registry), not purely spec-shape-specific. Hope that helps; happy to run the same package pair on any debug build.

  5. opencode-agent
    closed this as duplicateon Oct 27, 2026

  6. opencode-agent commented on Oct 27, 2026

    @opencode-agent
    opencode-agentBot
    on Oct 27, 2026 – with OpenCode Agent
    Contributor

    Closing this as a duplicate of #50080, since nobody has replied in the past day to say how it's different. #50080 covers the same failure: opencode-sdd-engram-manage as a bare name or @latest fails with NpmInstallFailedError (unable to resolve dependency tree at Npm.reify) and stops reconciliation on every start, while system npm installs it fine.

    Until it's fixed, pinning an exact version (e.g. [email protected]) is the reported workaround. Please follow #50080 for updates. A short comment there saying it still happens on 2.1.4 on Windows would help. If an exact version also fails for you, please reply here with the output and we can reopen. Thanks again for the thorough report!

  7. opencodejr
    reopened this on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    pending closetriaging

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions