opencode.json/config.json search path #3407

Activity

1. arlt

   added

   bugSomething isn't workingSomething isn't working

   on Oct 24, 2025
2. github-actions commented on Oct 24, 2025

   

   github-actionsBot

   on Oct 24, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • What's the proper way to pass current working directory to the global opencode.json config? #3395: What's the proper way to pass current working directory to the global opencode.json config? (discusses configuration file paths and usage)
   • Opencode adds stuff to global config folder #3191: Opencode adds stuff to global config folder (discusses configuration directory structure and file placement)
   • Glob patterns with ~/ expansion don't work in instructions configuration #3289: Glob patterns with / expansion don't work in instructions configuration (related to configuration file path handling)

   Feel free to ignore if none of these address your specific case about the extensive search path and /opencode.json placement.
3. rekram1-node commented on Oct 24, 2025

   

   rekram1-node

   on Oct 24, 2025

   Last edited by rekram1-node

   Collaborator

   More actions

   @arlt the config.json is legacy so we search it for backwards compatibility also we search 3 diffferent ones here because they are all supported:

   ~/.config/opencode/config.json
   ~/.config/opencode/opencode.json
   ~/.config/opencode/opencode.jsonc
   

   This is once again just for legacy support but we try to have most people use opencode.json or opencode.jsonc

   This code is what causes those other file paths tho:

       for (const file of ["opencode.jsonc", "opencode.json"]) {
         const found = await Filesystem.findUp(file, Instance.directory, Instance.worktree)
         for (const resolved of found.toReversed()) {
           result = mergeDeep(result, await loadFile(resolved))
         }
       }
   

   it just searches up the filesystem to check if you have any other opencode configs that it should be loading in, if you are in a git repo it should stop at the root of the repo, but if you are outside of a git repo it will look up to the global "/"

   This isn't a bug this is intentional behavior
4. arlt commented on Oct 24, 2025

   

   arlt

   on Oct 24, 2025

   Author

   More actions

   it just searches up the filesystem to check if you have any other opencode configs that it should be loading in, if you are in a git repo it should stop at the root of the repo, but if you are outside of a git repo it will look up to the global "/"

   This isn't a bug this is intentional behavior

   Ah - thanks for clarifying that.
5. arlt

   closed this as completedon Oct 24, 2025