Repository navigation
[FEATURE]: Allow plugins to have their own configuration #4393
Description
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"
],
}
Activity
github-actions commentedon Nov 17, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
airtonix commentedon Nov 17, 2025
Linked ticket doesn't address providing config to plugins via opencodes config file.
linked discord convo: https://discord.com/channels/1391832426048651334/1436485986501660863
GoodFarming commentedon Jan 18, 2026
I opened PR #9161 to add an optional top-level
plugin_configmap (plugin name -> arbitrary config).This enables plugin settings in
opencode.json(c)while keepingplugin: string[]semantics unchanged (lower-risk than changing thepluginarray shape).github-actions commentedon Mar 27, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.