anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #9161] feat(config): add plugin_config for structured plugin options #13012

New Issue
Open
opened 2026-02-16 18:17:53 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:17:53 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/9161

State: open
Merged: No

What does this PR do?

Adds an optional top-level plugin_config map to the config schema so plugins can receive structured options via opencode.json(c):

{
  "plugin": ["@acme/my-plugin"],
  "plugin_config": {
    "@acme/my-plugin": { "endpoint": "https://example.com" }
  }
}

Why?

Config parsing is strict (Config.Info is .strict()), so plugins can’t add plugin-specific keys to opencode.json(c) today without an upstream schema change. The common workarounds are env vars or sidecar config files, which are harder to install/standardize.

plugin_config is a minimal, additive escape hatch: OpenCode already passes the resolved config to plugins via Hooks.config, so plugins can read/validate their own entry without any new lifecycle plumbing.

Why this shape (vs plugin: [{ name, config }])?

Keeping plugin as a plain “load list” avoids changing plugin loading/deduping/merge semantics. plugin_config adds configuration without altering how plugins are resolved or initialized.

Notes

  • plugin_config is deep-merged across config layers (same merge behavior as other config objects).
  • Not intended for secrets; plugins should prefer existing auth/token flows when possible.

How did you verify your code works?

  • bun test --cwd packages/opencode
  • bun turbo typecheck
  • bun ./script/generate.ts

Fixes #4393

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/9161 **State:** open **Merged:** No --- ### What does this PR do? Adds an optional top-level `plugin_config` map to the config schema so plugins can receive structured options via `opencode.json(c)`: ```jsonc { "plugin": ["@acme/my-plugin"], "plugin_config": { "@acme/my-plugin": { "endpoint": "https://example.com" } } } ``` ### Why? Config parsing is strict (`Config.Info` is `.strict()`), so plugins can’t add plugin-specific keys to `opencode.json(c)` today without an upstream schema change. The common workarounds are env vars or sidecar config files, which are harder to install/standardize. `plugin_config` is a minimal, additive escape hatch: OpenCode already passes the resolved config to plugins via `Hooks.config`, so plugins can read/validate their own entry without any new lifecycle plumbing. ### Why this shape (vs `plugin: [{ name, config }]`)? Keeping `plugin` as a plain “load list” avoids changing plugin loading/deduping/merge semantics. `plugin_config` adds configuration without altering how plugins are resolved or initialized. ### Notes - `plugin_config` is deep-merged across config layers (same merge behavior as other config objects). - Not intended for secrets; plugins should prefer existing auth/token flows when possible. ### How did you verify your code works? - `bun test --cwd packages/opencode` - `bun turbo typecheck` - `bun ./script/generate.ts` Fixes #4393
yindo added the pull-request label 2026-02-16 18:17:53 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#13012
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?