[v2 Regression] Linux system configuration /etc/opencode/opencode.json is not discovered #55373

Activity

1. opencode-agent commented on Oct 14, 2026

   

   opencode-agentbot

   on Oct 14, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed report and the filesystem trace. I think this is a duplicate of #53074. v2.0.26 and v2.0.27 never look at the system config directory. Support for it was added in #54921 and first shipped in v2.0.28, so upgrading to the latest v2 (opencode upgrade) should make /etc/opencode/opencode.json load no matter which directory you run from.

   Possible duplicates and closely related issues, ordered from most to least likely:

   • /etc/opencode not respected in v2 #53074: /etc/opencode not respected in v2 (closed, fixed by fix(core): discover system configuration directory at lowest precedence #54921)
   • V2 does not load managed config from %ProgramData%\opencode (V1 managed settings) #51107: V2 does not load managed config from %ProgramData%\opencode. Same problem, reported for Windows and also fixed by fix(core): discover system configuration directory at lowest precedence #54921
   • fix(core): discover system configuration directory at lowest precedence #54921: the PR that adds system config discovery (/etc/opencode on Linux)

   One thing to know after upgrading: in v2, ordinary settings in the system config (providers, models and so on) are loaded at the lowest precedence, so they act as machine-wide defaults that user and project config can override. Only experimental.policies in that file outrank everything else.

   The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different, for example if it still happens on v2.0.28 or later.
2. opencode-agent

   added

   pending close

   triaging

   on Oct 14, 2026
3. pipoe2h commented on Oct 14, 2026

   

   pipoe2h

   on Oct 14, 2026

   Author

   More actions

   I've tried with 2.0.28 and 2.0.29, and the issue persists.
4. opencode-agent

   removed

   triaging

   pending close

   on Oct 14, 2026
5. opencode-agent commented on Oct 14, 2026

   

   opencode-agentbot

   on Oct 14, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for testing on 2.0.28 and 2.0.29. I couldn't reproduce this on 2.0.29. With a provider defined only in /etc/opencode/opencode.json (I tried both the v2 providers format and the v1 provider format), cd ~ && opencode models lists it.

   I could, however, get your exact symptom after an upgrade. OpenCode v2 runs a background service, and a service started by 2.0.26 kept running after I upgraded. The 2.0.29 CLI reused it: opencode --version said 2.0.29, but the old service still didn't read /etc/opencode. Restarting the service fixed it:

   opencode service restart   # or: opencode service stop, then run opencode again
   cd ~ && opencode models

   (On my machine service restart printed a "Server process … is still running" error but still replaced the old service. See #54267.)

   Could you try that and let us know whether the provider shows up? If it's still missing after a restart, please share:

   • the output of opencode --version and ps aux | grep '[o]pencode'
   • your /etc/opencode/opencode.json with secrets removed
   • the file's permissions (ls -l /etc/opencode/), and whether you run opencode as the same user who can read it
6. pipoe2h commented on Oct 14, 2026

   

   pipoe2h

   on Oct 14, 2026

   Author

   More actions

   Restarting the service solved the problem.
7. pipoe2h

   closed this as completedon Oct 14, 2026
8. opencode-agent commented on Oct 14, 2026

   

   opencode-agentbot

   on Oct 14, 2026 – with OpenCode Agent

   Contributor

   More actions

   Glad that sorted it, and thanks for confirming!

   To sum up: support for /etc/opencode was added in v2.0.28 (#54921). After you upgraded, the background service started by 2.0.26 was still running, and the new CLI kept using it, so the system config wasn't read until the service was restarted. If you upgrade OpenCode again, run opencode service restart afterwards so the service matches the new version.

   The old service outliving an upgrade is tracked separately, so you can follow it there:

   • upgrade: long-running serve from previous version keeps running after auto-update (404 on /api/status, service exits) #49664: a long-running service from the previous version keeps running after an upgrade
   • define managed service replacement authority across version skew #42212: how a managed service should be replaced when its version differs from the CLI
   • web: Settings/About version drifts from CLI version after upgrade #51112: version shown drifts from the CLI version after upgrading

   Since your problem is solved, the bot will close this issue soon. Reply here if it comes back.
9. opencode-agent

   closed this as not plannedon Oct 17, 2026
10. opencode-agent commented on Oct 17, 2026

    

    opencode-agentbot

    on Oct 17, 2026 – with OpenCode Agent

    Contributor

    More actions

    Closing this since you confirmed that restarting the background service fixed it. After the upgrade, a service started by 2.0.26 was still running; that version doesn't read /etc/opencode (support was added in v2.0.28, #54921). After future upgrades, run opencode service restart. The old service outliving an upgrade is tracked in #49664 and #42212. Thanks for the report and for testing. If /etc/opencode isn't picked up again even after a restart, please open a new issue with your version and steps.