OPENCODE_CONFIG_DIR is broken since 0.15.30 when only world-readable #3610

Activity

1. arlt

   added

   bugSomething isn't workingSomething isn't working

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

   

   github-actionsBot

   on Oct 31, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • [FEATURE]:global configuration /etc/opencode #3410: This feature request specifically discusses global configuration support in /etc/opencode and mentions configuration data should be searchable in both /etc/opencode and ~/.config/opencode/. Your use case aligns closely with what was requested in that issue.
   • [FEATURE]: custom config path to also support agent definition (via markdown) #3432: Discusses custom config path support via OPENCODE_CONFIG environment variable, which is related to your OPENCODE_CONFIG_DIR usage.

   Feel free to ignore if none of these address your specific case.
3. rekram1-node

   self-assigned this

   on Oct 31, 2025
4. rekram1-node commented on Oct 31, 2025

   

   rekram1-node

   on Oct 31, 2025

   Contributor

   More actions

   hm ill take a look
5. qwertologe commented on Nov 8, 2025

   

   qwertologe

   on Nov 8, 2025

   Last edited by qwertologe

   More actions

   @rekram1-node I used Qwen 3 for analysis (i hope this helps) - result:

   Root Cause

   The issue is in the installDependencies function in packages/opencode/src/config/config.ts at line 150 - link:

   if (!(await Bun.file(pkg).exists())) {  
     await Bun.write(pkg, "{}")  // This fails for read-only directories  
   }  

   When OpenCode loads a custom config directory via OPENCODE_CONFIG_DIR, it attempts to create a package.json file in that directory. If the directory is read-only (like /etc/opencode with 755 permissions), this write operation fails.

   Relevant Commit

   Concurrent Dependency Installation (commit c1ada30): Changed installDependencies calls to run concurrently using Promise.all for performance improvements

   Solution

   The installDependencies function should check directory write permissions before attempting to create files, or should handle permission errors gracefully when working with user-specified config directories.

   ---

   maybe?!:

   +    // Check if we have write permissions to the directory
   +    try {
   +      await fs.access(dir, fs.constants.W_OK)
   +    } catch {
   +      // If we don't have write permissions, skip installing dependencies
   +      log.debug("skipping dependency installation due to lack of write permissions", { path: dir })
   +      return
   +    }
   
6. rekram1-node commented on Nov 8, 2025

   

   rekram1-node

   on Nov 8, 2025

   Contributor

   More actions

   Yeah that looks fine, if u want u can open a pr and ill merge it since u found the issue, otherwise i can knock it out. Lmk ur preference @qwertologe
7. qwertologe commented on Nov 8, 2025

   

   qwertologe

   on Nov 8, 2025

   More actions

   @rekram1-node I really don't know if this is a good solution - maybe it would be better to fallback to project folder, ...

   I would really be glad if you can take over from here.
8. rekram1-node commented on Nov 8, 2025

   

   rekram1-node

   on Nov 8, 2025

   Contributor

   More actions

   sure will do thx @qwertologe just wanted to give u a chance to get the "credit" haha
9. thdxr

   closed this as completedon Mar 25, 2026