@weaveio/weave-adapter-opencode

@weaveio/weave-adapter-opencode

OpenCode adapter for Weave.

Installation

Add the adapter as a plugin in your opencode.json (or opencode.jsonc). Use the full versioned package specifier:

{
  "plugin": [
    "@weaveio/weave-adapter-opencode@0.0.1"
  ]
}

For preview/snapshot versions:

{
  "plugin": [
    "@weaveio/weave-adapter-opencode@0.0.0-preview-20260708134505"
  ]
}

OpenCode resolves the plugin from npm at startup, so the version must be pinned explicitly in the plugin array. There is no separate npm install step — OpenCode handles package fetching.

Local development

For local development, point OpenCode at the built dist/plugin.js via a file URL:

{
  "plugin": [
    "file:///abs/path/to/packages/adapters/opencode/dist/plugin.js"
  ]
}

Rebuild the package before using a dist/ file path so the plugin bundle matches the current source:

bun run --filter @weaveio/weave-adapter-opencode build

Isolated OpenCode validation

OpenCode merges global config, project config, explicit config, and plugin directories. OPENCODE_CONFIG and OPENCODE_CONFIG_CONTENT add config; they do not replace every other source by themselves.

To validate this adapter in isolation:

TMP_HOME="$(mktemp -d)"
TMP_XDG="$(mktemp -d)"

HOME="$TMP_HOME" \
XDG_CONFIG_HOME="$TMP_XDG" \
OPENCODE_DISABLE_PROJECT_CONFIG=1 \
OPENCODE_CONFIG_CONTENT='{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "file:///abs/path/to/packages/adapters/opencode/dist/plugin.js"
  ]
}' \
opencode debug config

Use the same environment with opencode debug info to verify that the plugin executes, not just that it appears in merged config.

Expected behavior

• opencode debug config should show the Weave-materialized agent map injected by the plugin's config hook.
• opencode debug info should show the plugin loading and executing.
• The resulting OpenCode agent entries should reflect the resolved Weave DSL for the loaded .weave/config.weave plus builtin Weave agent defaults.

Logging

When the plugin runs inside OpenCode, Weave logs are written to a file automatically instead of stdout. Writing structured JSON logs to stdout would surface raw log lines in the OpenCode UI, which is confusing for users.

Default log path: .weave/weave.log under the project directory (the same directory OpenCode passes as input.directory).

Override: set WEAVE_LOG_FILE=/absolute/path/to/weave.log in the environment to write logs to a custom path instead.

# Use the default path (.weave/weave.log in the project root)
opencode

# Override with a custom path
WEAVE_LOG_FILE=/tmp/weave-debug.log opencode

The log file is created automatically when the plugin starts. Parent directories are created if they do not exist. Logs are written synchronously (one write per log line) to ensure lines are visible immediately even if the process is killed.

Non-plugin usage: when @weaveio/weave-engine is used outside the OpenCode plugin path (e.g. in tests or other adapters), logs go to stdout by default unless WEAVE_LOG_FILE is set.