Opencode using up 380GB in ~/.local/share/opencode/snapshot/objects #9601

Activity

1. peterdonaghey

   added

   bugSomething isn't workingSomething isn't working

   on Jan 20, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 20, 2026
3. github-actions

   added

   perfIndicates a performance issue or need for optimizationIndicates a performance issue or need for optimization

   on Jan 20, 2026
4. github-actions commented on Jan 20, 2026

   

   github-actionsBot

   on Jan 20, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • HUGE snapshot folder #6845: HUGE snapshot folder (169GB in ~/.local/share/opencode/snapshot)
   • Snapshot feature needs safeguards for large directories (home directory filled disk) #8577: Snapshot feature needs safeguards for large directories (home directory filled disk)
   • [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation #8887: [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation
   • Very slow session due to 98GB of git snapshots #3182: Very slow session due to 98GB of git snapshots
   • [BUG] tmp_pack Files Consuming 180GB on Ubuntu 24.04 LTS #8749: [BUG] tmp_pack Files Consuming 180GB on Ubuntu 24.04 LTS

   All of these issues describe the same core problem: OpenCode's snapshot feature is consuming excessive disk space (100GB+) in ~/.local/share/opencode/snapshot/objects/. The root causes appear to be:

   1. Temporary pack files not being cleaned up
   2. Large directories (including ignored files) being tracked without safeguards
   3. Snapshot module ignoring watcher.ignore configuration

   Feel free to ignore if your specific case differs, but these existing issues may provide workarounds or context for the underlying problem.
5. peterdonaghey

   closed this as a duplicateof HUGE snapshot folder #6845 on Jan 20, 2026
6. lzqxd commented on Mar 25, 2026

   

   lzqxd

   on Mar 25, 2026

   More actions

   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.
7. piknockyou commented on Sep 30, 2026

   

   piknockyou

   on Sep 30, 2026

   More actions

   For anyone landing here: a global snapshot growing that large is usually the sign of sessions running in a broad folder - most commonly the home directory - rather than in a real project. Two quick checks from the folder where you start opencode:

   git rev-parse --show-toplevel - if it prints your home folder (or another broad parent folder) instead of a project, a stray/accidental .git there is the cause; delete it (usually empty; rename if unsure) and start opencode inside a real project folder. The oversized snapshots stop growing with it.

   If it prints a real project: git ls-files --others --exclude-standard | wc -l - if that is 100k+, move the heavy folders (node_modules, target, caches) into .gitignore, or set "snapshot": false in the config. (And as the comment above did: everything under ~/.local/share/opencode/snapshot/ is opencode's own store - it is safe to clear if it gets out of hand.)