You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Plugin directory without an entrypoint is dropped silently (V2) #58574
Follow-up to #44367 (closed as V1; could not be reopened by me), reproduced on V2 dev (c272a63cb4).
Problem: a directory listed in plugins that has no plugin entrypoint is dropped silently. A non-existent path in the same list is reported as failed (with error and ref), so the behavior is inconsistent and the user gets no hint why the plugin is not loaded.
Expected: the directory shows up as a failed plugin (GET /api/plugin, TUI toast, /plugins) like any other load failure.
Where:packages/core/src/config/plugin/source.ts (directory scan drops the entry without reporting).
I have a one-line fix plus a regression test ready locally (test fails before, passes after). Happy to open a PR referencing this issue.
Related, still only logged (not surfaced as failed): a configured path that is a file; an entrypoint that escapes the directory. Not part of the proposed fix.
Thanks for following up on V2 and tracing it to source.ts. I think this is a duplicate of #52300. That issue reports the same thing: a local plugin directory with no root entrypoint is skipped without any log or error. Its expected behaviour includes reporting that case clearly, which is what your fix does.
Possible duplicates and related issues, ordered by likelihood:
can confirm, same root cause as #52300. the drop is scan() in packages/core/src/config/plugin/source.ts:167, if (!entrypoints.server) return [] kills the operation with no failure recorded, while a nonexistent path passes through and shows up failed. send the PR against dev and reference #52300 so it lands on the canonical issue. keep the regression test.
We didn't hear back on how this differs from #52300, so I'm closing this as a duplicate. Both report a local plugin directory with no resolvable entrypoint being skipped without any warning or failed-plugin report. Please follow #52300 for updates. Your one-line fix and regression test would still be welcome as a PR that references #52300. If this turns out to be a different problem, reply here with the details and it can be reopened. Thanks again for the clear report!
Activity
opencode-agent commentedon Oct 24, 2026
Thanks for following up on V2 and tracing it to
source.ts. I think this is a duplicate of #52300. That issue reports the same thing: a local plugin directory with no root entrypoint is skipped without any log or error. Its expected behaviour includes reporting that case clearly, which is what your fix does.Possible duplicates and related issues, ordered by likelihood:
main/exportsto be honoured). Same problem.WARNlog line. This is the related case you mention as out of scope.Your fix and regression test would be welcome as a PR. Please reference #52300 so it's tracked in one place.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
benjaminkincses commentedon Oct 24, 2026
can confirm, same root cause as #52300. the drop is scan() in packages/core/src/config/plugin/source.ts:167,
if (!entrypoints.server) return []kills the operation with no failure recorded, while a nonexistent path passes through and shows up failed. send the PR against dev and reference #52300 so it lands on the canonical issue. keep the regression test.opencode-agent commentedon Oct 25, 2026
We didn't hear back on how this differs from #52300, so I'm closing this as a duplicate. Both report a local plugin directory with no resolvable entrypoint being skipped without any warning or failed-plugin report. Please follow #52300 for updates. Your one-line fix and regression test would still be welcome as a PR that references #52300. If this turns out to be a different problem, reply here with the details and it can be reopened. Thanks again for the clear report!