new terminal using opencode in home dir with snapshot: true will occupy huge storage #16336

Activity

1. Shana-AE

   added

   bugSomething isn't workingSomething isn't working

   on Mar 6, 2026
2. github-actions

   assigned

   thdxr

   on Mar 6, 2026
3. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   windows

   on Mar 6, 2026
4. github-actions commented on Mar 6, 2026

   

   github-actionsBot

   on Mar 6, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Why is OpenCode massively abusing git? #3176: OpenCode snapshotting large directories without size limits or permission — same root cause of snapshot running on a huge non-project directory
   • Snapshot system leaks tmp_pack_* files indefinitely, filling disk at ~9.5 GB/hour #14811: Snapshot system leaks tmp_pack files filling disk at ~9.5 GB/hour — related disk-filling behavior from snapshots
   • [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation #8887: Snapshot module ignoring config, causing excessive disk usage — related to snapshot running where it shouldn't

   If your issue is specifically about snapshot being triggered in a non-git/home directory rather than snapshot leaks, it may be distinct enough to keep open. Please review the above and let the maintainers know if this covers your case.
5. ahmad12-ui commented on Mar 7, 2026

   

   ahmad12-ui

   on Mar 7, 2026

   More actions

   Hi, I’m interested in working on this bug.
   If no one is currently fixing it, I’d like to investigate the issue and submit a PR.
6. vbuccigrossi

   added a commit that references this issue on Mar 7, 2026

   fix: resolve 4 bugs — Azure filters, snapshot safety, oxlint path, or…

   ...

   21e7a01
7. thdxr

   assigned

   rekram1-node

   and unassigned

   thdxr

   on Apr 26, 2026
8. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   windows

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on May 3, 2026
9. github-actions commented on Jul 3, 2026

   

   github-actionsBot

   on Jul 3, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
10. github-actions

    closed this as not plannedon Jul 3, 2026
11. piknockyou commented on Sep 30, 2026

    

    piknockyou

    on Sep 30, 2026

    More actions

    One addition for anyone landing here: before settling for "snapshot": false, check whether the home folder is accidentally a git repository - an accidental .git up there is a common reason home sessions start producing full snapshots.

    From the folder where you start opencode: git rev-parse --show-toplevel

    • If it prints your home folder (or another broad parent folder): that repo is almost certainly accidental - delete that .git (usually empty; rename if unsure) and start opencode inside a real project folder; the giant snapshot scan goes away with it, no config change needed.
    • If it reports no repository, or prints a real project of yours: then your plan applies - keep "snapshot": false globally and enable it per project where you want undo.

    For me the first case was it: a stray .git in home, and removing it ended the huge snapshots entirely.