Skip to content

[Bug]: npm plugins not loaded on v1.3.8 — "No plugin targets found", expects "oc-plugin" field in package.json #20139

Closed as not planned

Description

@alexzoo

Description

Description

After upgrading from v1.3.7 to v1.3.8, npm plugins are no longer loaded. Running opencode plugin <name> reports:

No plugin targets found
Expected: "oc-plugin": ["server", "tui"] or tuples like [["tui", { ... }]].
This affects all npm-based plugins that don't declare the new "oc-plugin" field in their package.json, including oh-my-opencode-slim, opencode-mystatus, and superpowers.

Steps to Reproduce

  1. Install v1.3.8 (opencode upgrade v1.3.8)
  2. Have an npm plugin in config (e.g. "plugin": ["oh-my-opencode-slim"])
  3. Run opencode plugin oh-my-opencode-slim
  4. Observe: "No plugin targets found"

Expected Behavior

Plugins that export a valid Plugin function (the previous standard) should be loaded, or there should be a fallback for backward compatibility.

Actual Behavior

Only plugins declaring "oc-plugin": ["server"] in package.json are loaded. The entire ecosystem of existing plugins is broken.

Workaround

Downgrade to v1.3.7:

opencode upgrade v1.3.7
bunx oh-my-opencode-slim@latest install --reset --no-tui
After downgrade, all plugins load normally.
Environment
- macOS Apple Silicon
- OpenCode v1.3.8 (broken) / v1.3.7 (working)
- Plugin: oh-my-opencode-slim 0.9.0
Additional Context
The PluginModule type in @opencode-ai/plugin@1.3.8 now expects { server: Plugin } instead of a bare Plugin export. This appears to be introduced in v1.3.4 ("Add single target plugin entrypoints") but plugins in the ecosystem haven't adapted yet.

### Plugins

oh-my-opencode-slim 0.9.0

### OpenCode version

v1.3.8

### Steps to reproduce

Steps to Reproduce
Install v1.3.8 (opencode upgrade v1.3.8)
Have an npm plugin in config (e.g. "plugin": ["oh-my-opencode-slim"])
Run opencode plugin oh-my-opencode-slim
Observe: "No plugin targets found"
Expected Behavior
Plugins that export a valid Plugin function (the previous standard) should be loaded, or there should be a fallback for backward compatibility.

Actual Behavior
Only plugins declaring "oc-plugin": ["server"] in package.json are loaded. The entire ecosystem of existing plugins is broken.

### Screenshot and/or share link

_No response_

### Operating System

macOS Apple Silicon

### Terminal

_No response_

Activity

  1. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Mar 30, 2026
  2. erkanercan commented on Mar 30, 2026

    @erkanercan

    A workaround and temporary fix for the same related issue at griffinmartin/opencode-claude-auth#101 (comment)

  3. erkanercan commented on Mar 30, 2026

    @erkanercan
  4. jd-apprentice commented on Apr 2, 2026

    @jd-apprentice
  5. DenisBalan commented on Apr 25, 2026

    @DenisBalan

    same happening now

    :/tmp/qq$ opencode --log-level DEBUG --print-logs plugin oh-my-opencode-slim@latest
    
    INFO  2026-04-25T19:23:21 +264ms service=server-proxy version=1.14.25 args=["--log-level","DEBUG","--print-logs","plugin","oh-my-opencode-slim@latest"] process_role=main run_id=6697173f-f9c3-40f5-81c0-568eb12c572f opencode
    
    ┌  Install plugin oh-my-opencode-slim@latest
    INFO  2026-04-25T19:23:21 +1ms service=server-proxy directory=/tmp/qq creating instance
    INFO  2026-04-25T19:23:21 +3ms service=project directory=/tmp/qq fromDirectory
    INFO  2026-04-25T19:23:21 +4ms service=db path=/home/qqq/.local/share/opencode/opencode.db opening database
    INFO  2026-04-25T19:23:21 +2ms service=db count=13 mode=bundled applying migrations
    │
    ◇  Plugin package ready
    │
    ■  Manifest read failed
    │
    ■  Installed "oh-my-opencode-slim@latest" but failed to read /home/qqq/.cache/opencode/packages/oh-my-opencode-slim@latest/node_modules/oh-my-opencode-slim
    │
    ■  ENOENT: no such file or directory, open '/home/qqq/.cache/opencode/packages/oh-my-opencode-slim@latest/node_modules/package.json'
    │
    └  Done
    
    
  6. removed
    bugSomething isn't working
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  7. github-actions commented on Jul 4, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions