[FEATURE]: Allow plugins to have their own configuration #2909

Open
opened 2026-02-16 17:37:45 -05:00 by yindo · 3 comments
Owner

Originally created by @airtonix on GitHub (Nov 16, 2025).

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Currently we can use plugins like:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["opencode-skills", "opencode-sessions"],
}

But it occurs to me that some plugins would benefit from allowing the user to configure them differently:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    { "name": "opencode-skills", "config": { "paths": [ "~/Dotfiles/OpencodeSkills" ] } },
    "opencode-sessions"
  ],
}
Originally created by @airtonix on GitHub (Nov 16, 2025). ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Currently we can use plugins like: ```json { "$schema": "https://opencode.ai/config.json", "plugin": ["opencode-skills", "opencode-sessions"], } ``` But it occurs to me that some plugins would benefit from allowing the user to configure them differently: ```json { "$schema": "https://opencode.ai/config.json", "plugin": [ { "name": "opencode-skills", "config": { "paths": [ "~/Dotfiles/OpencodeSkills" ] } }, "opencode-sessions" ], } ```
yindo added the discussion label 2026-02-16 17:37:45 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Nov 16, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #753: Features a comprehensive extensible plugin system that includes plugin configuration capabilities, though it's currently closed

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Nov 16, 2025): This issue might be a duplicate of existing issues. Please check: - #753: Features a comprehensive extensible plugin system that includes plugin configuration capabilities, though it's currently closed Feel free to ignore if none of these address your specific case.
Author
Owner

@airtonix commented on GitHub (Nov 16, 2025):

Linked ticket doesn't address providing config to plugins via opencodes config file.

linked discord convo: https://discord.com/channels/1391832426048651334/1436485986501660863

@airtonix commented on GitHub (Nov 16, 2025): Linked ticket doesn't address providing config to plugins via opencodes config file. linked discord convo: https://discord.com/channels/1391832426048651334/1436485986501660863
Author
Owner

@GoodFarming commented on GitHub (Jan 17, 2026):

I opened PR #9161 to add an optional top-level plugin_config map (plugin name -> arbitrary config).

This enables plugin settings in opencode.json(c) while keeping plugin: string[] semantics unchanged (lower-risk than changing the plugin array shape).

@GoodFarming commented on GitHub (Jan 17, 2026): I opened PR #9161 to add an optional top-level `plugin_config` map (plugin name -> arbitrary config). This enables plugin settings in `opencode.json(c)` while keeping `plugin: string[]` semantics unchanged (lower-risk than changing the `plugin` array shape).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2909