You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Config autoupdate only respected at global path #6984
Config file includes "autoupdate": false,, but v1.1.1 ignores this and updates to v1.1.2 on startup.
This occurs whether using ~/.config/opencode/opencode.json, a local path ./opencode.json and referencing the env var OPENCODE_CONFIG to declare a specific config.
This did not occur on v1.0.223 or earlier.
Autoupdate also occurs automatically if "autoupdate": "notify" is specified.
It appears there may be a broader regression in v1.1.1 where configuration settings from opencode.json are not being properly respected on startup. Feel free to ignore if your specific case differs from these issues.
this seems to stop the autoupdate from occurring. it's a band-aid fix, but nice to know this works. definitely preferred to have this in a config file, though.
OPENCODE_CONFIG=opencode-autodate.json OPENCODE_DISABLE_AUTOUPDATE=true opencode # no auto update
NOTE: autoupdate still occurs automatically with notify, quoted or otherwise. i'd still rather just have this disabled and manually update when i'm ready (because you're so quick to churn out updates!), but i've yet to actually see the notification that the doc mentions.
OPENCODE_CONFIG=opencode-autodate.json OPENCODE_DISABLE_AUTOUPDATE="notify" opencode # auto updates OPENCODE_CONFIG=opencode-autodate.json OPENCODE_DISABLE_AUTOUPDATE=notify opencode # auto updates
hmm... the config is the first step i shared in in steps to reproduce... is the config not picking this up for some reason. i didn't run into this issue prior to version 1.1.1
Edit: oh, interesting... i've been pretty diligent with manually updating to the latest when i fire up new sessions.. and didn't realize that this actually had been occurring for a while. the difference was that back when i was on e.g. 1.0.80, autoupdate would occur, but there was no user notification. i've updated a few times since, but that would have been manually, so i wouldn't have seen a new release.
What this tells me is that the autoupdate boolean (or sometimes a string for notify, which is an interesting choice) doesn't care about the config value that's being set. the shell env var OPENCODE_DISABLE_AUTOUPDATE is a band-aid for the time being, but would prefer to not rely on that long-term. also with so much rapid release going on in this project, i really don't want to be caught off guard with an unintended version update.
It seems this is directly related to where the config file exists. The only way "autoupdate": false seems to be respected, is if it's in the default ~/.config/opencode/opencode.json location. I've now confirmed this up to v1.1.5.
confirmed: only if config file is at the default path, opencode does not autoupdate
opencode --version
1.1.5
To test, you should be able to simply copy/paste either code block with the same results. I've been able to successfully confirm this on macOS Sequoia and Ubuntu 22.04 LTS.
Activity
github-actions commentedon Jan 5, 2026
This issue might be a duplicate of existing issues. Please check:
It appears there may be a broader regression in v1.1.1 where configuration settings from opencode.json are not being properly respected on startup. Feel free to ignore if your specific case differs from these issues.
rekram1-node commentedon Jan 5, 2026
Can u share full config? None of that code changed between versions as far as I can tell
You can also try:
OPENCODE_DISABLE_AUTOUPDATE=true
scottrbaxter commentedon Jan 5, 2026
this seems to stop the autoupdate from occurring. it's a band-aid fix, but nice to know this works. definitely preferred to have this in a config file, though.
OPENCODE_CONFIG=opencode-autodate.json OPENCODE_DISABLE_AUTOUPDATE=true opencode# no auto updateNOTE: autoupdate still occurs automatically with notify, quoted or otherwise. i'd still rather just have this disabled and manually update when i'm ready (because you're so quick to churn out updates!), but i've yet to actually see the notification that the doc mentions.
OPENCODE_CONFIG=opencode-autodate.json OPENCODE_DISABLE_AUTOUPDATE="notify" opencode# auto updatesOPENCODE_CONFIG=opencode-autodate.json OPENCODE_DISABLE_AUTOUPDATE=notify opencode# auto updatesrekram1-node commentedon Jan 5, 2026
okay but in ur config I dont see autoupdate set to false anywhere
scottrbaxter commentedon Jan 5, 2026
hmm... the config is the first step i shared in in steps to reproduce... is the config not picking this up for some reason. i didn't run into this issue prior to version
1.1.1Edit: oh, interesting... i've been pretty diligent with manually updating to the latest when i fire up new sessions.. and didn't realize that this actually had been occurring for a while. the difference was that back when i was on e.g.
1.0.80, autoupdate would occur, but there was no user notification. i've updated a few times since, but that would have been manually, so i wouldn't have seen a new release.What this tells me is that the
autoupdateboolean (or sometimes a string fornotify, which is an interesting choice) doesn't care about the config value that's being set. the shell env varOPENCODE_DISABLE_AUTOUPDATEis a band-aid for the time being, but would prefer to not rely on that long-term. also with so much rapid release going on in this project, i really don't want to be caught off guard with an unintended version update.scottrbaxter commentedon Jan 7, 2026
It seems this is directly related to where the config file exists. The only way
"autoupdate": falseseems to be respected, is if it's in the default~/.config/opencode/opencode.jsonlocation. I've now confirmed this up tov1.1.5.e.g.
local path
Auto update occurs
default path
no autoupdate
confirmed: only if config file is at the default path, opencode does not autoupdate
To test, you should be able to simply copy/paste either code block with the same results. I've been able to successfully confirm this on macOS Sequoia and Ubuntu 22.04 LTS.
rekram1-node commentedon Jan 7, 2026
ill check it, hmmm
[-]Config autoupdate not respected on v1.1.1[/-][+]Config autoupdate only respected at global path[/+]fix: PATCH /config writes to correct project config file
thdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
epark001 commentedon Apr 21, 2026
this issue is still occurring for me as well