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
This is the intended behavior when the snapshot feature is enabled.
You may disable the snapshot feature if you would like to by putting the following in your opencode.json configuration file: "snapshot": false,, but doing so means that the /undo and /redo commands will no longer reverse changes to files as a consequence.
@rekram1-node Neat! I disabled snapshots locally in my own configuration months ago and had not realized that this cleanup feature had been added, I'm going to try re-enabling It immediately and see how much space it ends up taking now. It would be even cooler if the duration for which they were kept could be configured in days.
@rekram1-node* Neat! I disabled snapshots locally in my own configuration months ago and had not realized that this cleanup feature had been added, I'm going to try re-enabling It immediately and see how much space it ends up taking now. It would be even cooler if the duration for which they were kept could be configured in days.
Can you check if #10248 bug no one seems to reply to him
This "Git" process snapshot take 30MB/s READ & WRITE respectively, no matter what he is doing it is a performance killer when i am bulk loading data to database
While /redo and /undo take the important role in opencode UX. It is highly recommended to online history cleanup module by session as mentioned in https://github.com/anomalyco/opencode/issues/4980. Not all history deserves redo and undo protection.
Ok, the snapshot feature is a must, I cannot work without this. Not sure why specifically today with opus 4.6 it's getting out of control (need to cache 60gb every 10 minutes...).
Also, what's weird is that I had the feeling the cache was growing when agents were simply making search queries in files and codebase, not because of code changes, but I am probably wrong.
However, with swarm agents coming probably eventually, I think it's a must to be able to specify a cache folder on another drive, this can compromise system for users not putting opencode in a sandbox environment. Thank
Activity
github-actions commentedon Jan 25, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
ariane-emory commentedon Jan 26, 2026
This is the intended behavior when the snapshot feature is enabled.
You may disable the snapshot feature if you would like to by putting the following in your
opencode.jsonconfiguration file:"snapshot": false,, but doing so means that the/undoand/redocommands will no longer reverse changes to files as a consequence.rekram1-node commentedon Jan 26, 2026
We auto cleanup snapshots every 7 days, we could make it more frequently
ariane-emory commentedon Jan 26, 2026
@rekram1-node Neat! I disabled snapshots locally in my own configuration months ago and had not realized that this cleanup feature had been added, I'm going to try re-enabling It immediately and see how much space it ends up taking now. It would be even cooler if the duration for which they were kept could be configured in days.
cravenceiling commentedon Jan 26, 2026
Maybe add a config for this?
rekram1-node commentedon Jan 26, 2026
Yeah
jsrcode commentedon Jan 26, 2026
Can you check if #10248 bug no one seems to reply to him
jsrcode commentedon Jan 26, 2026
Can you check if #10248 bug no one seems to reply to him
ariane-emory commentedon Jan 26, 2026
@jsrcode Sadly I do not have access to Windows, sorry.
allanchan339 commentedon Feb 4, 2026
This "Git" process snapshot take 30MB/s READ & WRITE respectively, no matter what he is doing it is a performance killer when i am bulk loading data to database
While
/redoand/undotake the important role in opencode UX. It is highly recommended to online history cleanup module by session as mentioned inhttps://github.com/anomalyco/opencode/issues/4980. Not all history deserves redo and undo protection.IM-001 commentedon Feb 8, 2026
Ok, the snapshot feature is a must, I cannot work without this. Not sure why specifically today with opus 4.6 it's getting out of control (need to cache 60gb every 10 minutes...).
Also, what's weird is that I had the feeling the cache was growing when agents were simply making search queries in files and codebase, not because of code changes, but I am probably wrong.
However, with swarm agents coming probably eventually, I think it's a must to be able to specify a cache folder on another drive, this can compromise system for users not putting opencode in a sandbox environment. Thank
IM-001 commentedon Feb 9, 2026
#12708 (comment)
github-actions commentedon Apr 10, 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.