Repository navigation
[FEATURE]: Composable configs #8241
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
Hi team, thanks for the amazing product.
At the global level we have ~/.config/opencode/config.json.
It'd be awesome if we can compose other configs into this. So the config.json can become like
{
...
"extends": [
// Extend from a local config
"~/workspace/my-opencode-config",
// Extend from a git repository
'github:someone/awesome-opencode-config',
// Extend from a git repository
'github:someone/awesome-opencode-config#v1', // we can specify a tag via #v1
]
}
As the opencode community grows, this composable config will be really useful.
Of course, there's a problem of "how to merge many configs if they have conflicting keys", but let me create an issue here to initiate the discussion.
I hope others find this request useful.
Activity
github-actions commentedon Jan 13, 2026
This issue might be a duplicate of existing issues. Please check:
These issues relate to making configs more composable, reusable, and shareable. The composable config feature in #8241 would likely help address the concerns raised in these issues.
Feel free to ignore if none of these address your specific case.
thdxr commentedon Mar 25, 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.