[Bug]: Plugin silently fails to load — runtime value-import of @opencode-ai/plugin unresolved in plugin cache

[jwhandy3]

Bug Description

On opencode 1.17.14, DCP 3.1.14 silently fails to load: no compress tool, no /dcp panel, and no debug logs are written even with "debug": true. ~/.config/opencode/logs/dcp/context/ gets no new session entries.
Root cause: the compiled entry dist/index.js does a runtime value import import { tool } from "@opencode-ai/plugin"; (2 occurrences). opencode installs DCP into ~/.cache/opencode/packages/@tarquinen/opencode-dcp@latest/node_modules/, where only @opencode-ai/sdk exists under @opencode-ai/ — @opencode-ai/plugin is missing (it's only a peer/dev dependency, so opencode's installer never provides it). ESM imports are hoisted, so the unresolved import throws before any DCP code runs; opencode's loader catches it in its dynamic-import try/catch and drops the plugin with nothing surfaced. Regressed after opencode's namespaced-hook plugin refactor (~2026-06-22) stopped making @opencode-ai/plugin resolvable from the plugin cache. Plugins that reference the SDK with import type only are unaffected (type imports are erased at runtime).
Reproduction:
node --input-type=module -e "import('file://$HOME/.cache/opencode/packages/@tarquinen/opencode-dcp@latest/node_modules/@tarquinen/opencode-dcp/dist/index.js').then(()=>console.log('OK')).catch(e=>console.log('ERR:',e.message))"

ERR: Cannot find package '@opencode-ai/plugin'

Confirmed workaround:
npm install @opencode-ai/plugin@1.15.5 --prefix "$HOME/.cache/opencode/packages/@tarquinen/opencode-dcp@latest"
After restart: DCP initialized logs and the compress tool appear. Suggested fix: bundle tool via tsup noExternal: ["@opencode-ai/plugin"], or promote @opencode-ai/plugin to a direct dependency.

Expected Behavior

DCP loads, writes DCP initialized to the daily log, and registers the compress tool — without the user having to manually install @opencode-ai/plugin into the plugin cache.

Debug Context Logs

During the failure, no context log JSON is produced at all — that's the symptom (import throws before DCP runs). Evidence instead comes from the daily log gap and the reproduction. Paste this:
{
  "note": "No context log generated while broken — the module throws on import before DCP executes.",
  "daily_log_evidence": [
    "~/.config/opencode/logs/dcp/daily/2026-06-17.log: last line = 'DCP initialized' (then nothing for ~19 days across multiple restarts)",
    "After installing @opencode-ai/plugin into the cache, 2026-07-06.log immediately shows: 'DCP initialized', 'Cached model context limit | limit=1000000', 'Recorded compression start', 'Marked 44 duplicate tool calls for pruning', 'Saved session state to disk | totalTokensSaved=202237'"
  ],
  "import_repro": "ERR: Cannot find package '@opencode-ai/plugin'"
}
(Optional: to attach a real post-fix context log, grab the newest file under ~/.config/opencode/logs/dcp/context/<session>/<timestamp>.json.)

Tool Call Details

N/A — the compress tool was never registered because the plugin never loaded. No tool call was possible until the workaround was applied.

DCP Version

3.1.14

Opencode Version

1.17.14

Model

Claude Sonnet 4

Additional Context

Same class of silent-load-failure as #575 (missing tiktoken). The distinguishing factor here is a value import of @opencode-ai/plugin (vs. import type), which only breaks post the opencode plugin-loader refactor. opencode fork: github.com/anomalyco/opencode.

[Elisiac]

Hello. I confirm he bug is still present. I was just about to write the bug report when I found this one. SO adding it here for completeness.

DCP silently fails to load on opencode 1.18.13 — @opencode-ai/plugin peer dependency not resolvable

Summary

@tarquinen/opencode-dcp@3.1.14 silently fails to register its compress tool after upgrading opencode from 1.18.10 to 1.18.13. The plugin appears in opencode debug info and debug config as loaded, but no tools are registered and no errors are logged. The root cause is that @opencode-ai/plugin — declared as a peerDependency in DCP — is no longer resolvable from DCP's install location, so the plugin's entry module fails on its first import and opencode swallows the failure.

Environment

Component	Version
opencode	1.18.13 (upgraded from 1.18.10)
@tarquinen/opencode-dcp	3.1.14
OS	Linux 6.8.0-137-generic x64
opencode plugin install scope	global (~/.config/opencode/opencode.jsonc)
DCP config	~/.config/opencode/dcp.jsonc (enabled: true, compress mode range, permission allow)

Symptom

DCP's compress tool is not registered at runtime despite the plugin being listed as loaded.

Before (opencode 1.18.10) — working

$ opencode debug agent "<agent>" 2>&1 | grep compress
      "permission": "compress",
    "compress": true

# opencode log — Aug 4 (v1.18.10)
timestamp=2026-08-04T08:57:36.955Z ... command=... command=dcp-compress agent="Sisyphus - ultraworker"
timestamp=2026-08-04T11:45:43.011Z ... command=... command=dcp-compress agent="Atlas - Plan Executor"
timestamp=2026-08-04T11:30:36.190Z ... command=... command=dcp-compress agent="Sisyphus - ultraworker"
# 10+ "permission=compress" evaluations across the day

After (opencode 1.18.13) — broken

$ opencode debug agent "<agent>" 2>&1 | grep compress
# (no output)

# opencode log — Aug 5 (v1.18.13)
# zero "permission=compress" evaluations
# zero "dcp-compress" command invocations

The session hit the context limit because DCP was not pruning:

timestamp=2026-08-05T08:20:19.781Z level=ERROR ...
  error="This model's maximum context length is 262144 tokens. However, you requested
  26000 output tokens and your prompt contains at least 236145 input tokens..."

Root Cause

1. DCP declares @opencode-ai/plugin as a peer dependency, not a regular dependency

package.json:

{
  "peerDependencies": {
    "@opencode-ai/plugin": ">=1.4.3",
    "@opentui/core": "^0.4.2",
    "@opentui/solid": "^0.4.2",
    "solid-js": "^1.9.12"
  },
  "dependencies": {
    "@anthropic-ai/tokenizer": "^0.0.4",
    "@opencode-ai/sdk": "^1.4.3",
    "jsonc-parser": "^3.3.1"
  }
}

Only @opencode-ai/sdk is a regular dependency and gets installed into node_modules/@opencode-ai/sdk. @opencode-ai/plugin is expected to be provided by the host.

2. opencode 1.18.13 does not make @opencode-ai/plugin resolvable from the plugin's install directory

opencode installs plugins under ~/.cache/opencode/packages/<spec>/. After the 1.18.13 upgrade, DCP's node_modules contains only sdk:

$ ls ~/.cache/opencode/packages/@tarquinen/opencode-dcp@latest/node_modules/@opencode-ai/
sdk

A copy of @opencode-ai/plugin@1.15.13 exists at ~/.opencode/node_modules/@opencode-ai/plugin, but it is not on the module resolution path that the plugin entry point uses. The DCP entry module starts with:

// dist/index.js (line 1598)
import { tool } from "@opencode-ai/plugin";

This import fails to resolve and the entire plugin module fails to load. Node/Bun confirm the resolution failure:

$ node -e "require.resolve('@opencode-ai/plugin', {
  paths: ['/home/echessel/.cache/opencode/packages/@tarquinen/opencode-dcp@latest/node_modules/@tarquinen/opencode-dcp']
})"
Failed: Cannot find module '@opencode-ai/plugin'

3. opencode swallows the plugin load failure

There is no level=ERROR or level=WARN log line for DCP failing to load. opencode debug info still lists DCP among active plugins:

plugins:
- oh-my-openagent@latest
- opencode-mem@latest
- @tarquinen/opencode-dcp@latest

This is what makes the bug silent: the plugin is "registered" from opencode's perspective (its spec is in the config and the package was installed), but its hooks and tools never register because the module never executes.

4. Contrast with opencode-mem — which works

I also use another pluginopencode-mem which declares @opencode-ai/plugin as a regular dependency and it works just fine:

{
  "dependencies": {
    "@opencode-ai/plugin": "^1.18.4",
    "@opencode-ai/sdk": "^1.18.4",
    ...
  }
}

Its package-lock.json installs @opencode-ai/plugin@1.18.13 into its own node_modules, so its import resolves and the plugin loads. DCP's package-lock.json does not include @opencode-ai/plugin at all.

Verification of the Fix

Installing @opencode-ai/plugin into DCP's local node_modules restores the plugin:

$ npm install @opencode-ai/plugin@1.18.13 --no-save --legacy-peer-deps \
    --prefix ~/.cache/opencode/packages/@tarquinen/opencode-dcp@latest/node_modules/@tarquinen/opencode-dcp

$ node --input-type=module -e "
  const mod = await import('/home/.../@tarquinen/opencode-dcp@latest/node_modules/@tarquinen/opencode-dcp/dist/index.js');
  console.log('LOADED OK. Exports:', Object.keys(mod));
"
LOADED OK. Exports: [ 'default' ]

After the fix, the compress tool is registered in a fresh opencode session:

$ opencode debug agent "<agent>" 2>&1 | grep -A40 '"tools":' | tail -5
    "interactive_bash": true,
    "memory": true,
    "compress": true
  }
}

Impact

• Silent failure. No log line, no banner. Users upgrading opencode lose DCP without knowing.
• Context overflow. With native compaction disabled ("compaction": { "auto": false }) — the recommended DCP setup — sessions run until they hit the model's context limit and crash.
• Misleading diagnostics. opencode debug info and opencode debug config report DCP as loaded.

Recommended Fix (on the maintainer side)

One of:

1. Move @opencode-ai/plugin from peerDependencies to dependencies in package.json. This guarantees it is installed into DCP's node_modules and is the approach opencode-mem takes. Lowest risk, no host coordination needed.

2. Keep it as a peer dependency but document the install requirement and emit a startup log line when the import fails so the failure is not silent. The plugin already has a Logger class; a logger.error("DCP failed to load: @opencode-ai/plugin not resolvable, ...") in a try/catch around the server function body would make this diagnosable.

3. Pin @opencode-ai/plugin to a version range that is known to ship the APIs DCP uses and add it to bundledDependencies so the exact copy ships with the npm tarball.

Recommended Fix (from the user side, workaround while this is patched)

Until the plugin is patched, you can install the missing peer dependency manually:

npm install @opencode-ai/plugin@<opencode-version> --no-save --legacy-peer-deps \
  --prefix ~/.cache/opencode/packages/@tarquinen/opencode-dcp@latest/node_modules/@tarquinen/opencode-dcp

Then restart opencode. This needs to be reapplied after every DCP reinstall.

Reproduction

1. Install opencode 1.18.13.
2. opencode plugin @tarquinen/opencode-dcp@latest --global.
3. Start a session and run opencode debug agent "<agent>" 2>&1 | grep compress — no output.
4. Check ~/.local/share/opencode/log/opencode.log for the session — no DCP init log, no permission=compress evaluations.
5. Confirm DCP's node_modules/@opencode-ai/ contains only sdk, not plugin.

[acramsay]

I'm hitting the same issue on 3.1.14 but at install time rather than runtime with opencode 1.17.14 (linux). Arborist fails to resolve the @opentui/core, @opentui/solid, and solid-js peer deps and the plugin just isn't installed at all. At runtime, this presents as a "No such file or directory" popup error in the TUI.

Until this is solve, I'm pinning to 3.1.13 which still works fine. I'd love to see this one fixed!