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
Hi,
I was setting up a nixos vm and found that I had way less space on my disk than usual but I didn't download anything very big for a while.
So I launched filelight to see what was going on and turns out the ~/.local/share/opencode folder was 169gb!!!!!
Sorry, but wtf, how is that even possible. 😂
It seems to be stuff in ~/.local/share/opencode/snapshot/global/objects/pack
Is it a known issue, I didn't really find anything ?
I update opencode almost always the day or next day when there is an update, so maybe it was a bug in earlier versions ?
according to #9290 (comment) it should be fixed but I think a filter to ignore tracking for massive files and snapshot folder watching and alert is actually appropriate, currently this is dangerous when working in folders with large datasets (not even tracked with git).
My opencode also had the same issue. I simply deleted all the hash files in the snapshot/global/objects directory, and then when I used opencode again, there was no problem anymore.
This should be fixed by commit 0a80ef4 which adds a 2MB file size limit for snapshotting. Files over 2MB are now excluded from git snapshots.
@thdxr Thanks for the info. However said commit doesn't solve the problem if you have a huge repo with many files < 2MB. I'd like to suggest for a configurable hard cap (e.g. per workspace) for snapshots.
Activity
ja-mf commentedon Jan 21, 2026
same here, this was a session lasting 1-2 days
according to #9290 (comment) it should be fixed but I think a filter to ignore tracking for massive files and snapshot folder watching and alert is actually appropriate, currently this is dangerous when working in folders with large datasets (not even tracked with git).
miguelnavarro89 commentedon Jan 22, 2026
same for me, opencode is basically useless unless I remove snapshot folder every hour.
rekram1-node commentedon Jan 22, 2026
@miguelnavarro89 it has been released, and yes u can disable snapshotting just do:
snapshot: false in ur opencode.json
opencode: Update to Claude Opus 4.6, disable snapshot
feat: auto-cleanup stale OpenCode snapshot tmp_pack files on startup
Cyberistic commentedon Mar 20, 2026
if you're doing any kind of ML training, do NOT leave opencode open while it trains and saves weights. 😵💫
StephenAnboer commentedon Mar 21, 2026
my .local\share\opencode\snapshot\global\objects was 300gb, ran out all of my C
lzqxd commentedon Mar 25, 2026
My opencode also had the same issue. I simply deleted all the hash files in the snapshot/global/objects directory, and then when I used opencode again, there was no problem anymore.
thdxr commentedon Mar 25, 2026
This should be fixed by commit 0a80ef4 which adds a 2MB file size limit for snapshotting. Files over 2MB are now excluded from git snapshots.
jialigit2 commentedon Mar 25, 2026
why this issue is closed, opencode crashes for the disk full issue very often. very annoying. which version is fixed for this?
erikdemarco commentedon Apr 26, 2026
It doesn't.
xWTF commentedon Jun 15, 2026
@thdxr Thanks for the info. However said commit doesn't solve the problem if you have a huge repo with many files < 2MB. I'd like to suggest for a configurable hard cap (e.g. per workspace) for snapshots.
For example:
feat: auto-cleanup stale OpenCode snapshot tmp_pack files on startup