anomalyco / anomalyco/opencode

[FEATURE]: allow specification of additional configuration directories via project-local configuration

Open
#45,811 1 comment 0 reactions 1 assignee View on GitHub

@nexxeln is already working on this.

Since Aug 28, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

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

I would like to create a new project which is already set up to use a specific set of configuration, but I don't want to copy that configuration boilerplate into the project each time. The most straightforward way to do this would be to add an option to opencode.json so That I could create the new one with

{
  "$schema": "https://opencode.ai/config.json",
  "extraConfigDirs": [
    "/one/path",
    "/another/path",
    "/a/third/path"
  ]
}

And it would be as if I created a new project with a bunch of boilerplate skills and commands under .opencode, but without actual boilerplate.

This is most similar to #26051 (closed for inactivity), except that it asks that we support a config file setting rather than an environment variable. Both are good, but for different use-cases.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.