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

[FEATURE]: Composable configs #5364

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

Originally created by @eunjae-lee on GitHub (Jan 13, 2026).

Originally assigned to: @thdxr on GitHub.

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.

Originally created by @eunjae-lee on GitHub (Jan 13, 2026). Originally assigned to: @thdxr on GitHub. ### 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 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.
yindo added the discussion label 2026-02-16 17:51:52 -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 discussion
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#5364
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?