anomalyco / anomalyco/opencode

[FEATURE]: Add content-only configuration authority for embedded runtimes

Open
#45,492 0 comments 0 reactions 1 assignee View on GitHub

@nexxeln is already working on this.

Since Aug 27, 2026.

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

Description

Feature hasn't been suggested before.
  • I verified that this exact feature has not been suggested before.
Describe the enhancement you want to request

I run OpenCode as a child process and pass the whole config through
OPENCODE_CONFIG_CONTENT. I expected that to be the final config, but it
isn't. Account config, managed files or preferences, and discovered config
directories are loaded later, so they can change the provider or add plugins.

Could there be an opt-in flag that treats OPENCODE_CONFIG_CONTENT as the only
config source? In that mode OpenCode would skip the usual config discovery and
dependency install. It shouldn't touch existing config files, and launches
without the flag should behave as they do now.

#43227 is close, but --bare intentionally keeps managed configuration and
only covers opencode run. #21264 only disables global config. I'm looking for
the same kind of isolation when OpenCode is embedded as a child process.

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.