Repository navigation
Snapshot feature needs safeguards for large directories (home directory filled disk) #8577
Description
The snapshot feature runs git add . on the entire worktree without any size or path checks. When .git exists in a large directory (like home), this causes severe disk exhaustion.
What happened
- Accidentally had
.gitin home directory (~) - Ran
opencode .from home - Snapshot started tracking entire home directory (112GB)
- Disk went from 44GB free → nearly 0 within minutes
- CPU pinned at 100% from continuous
git add . - System became unresponsive - couldn't make any changes, had to delete cache just to recover
- Had to manually
pkill -9git processes and delete~/.local/share/opencode/snapshot/
Root cause
packages/opencode/src/snapshot/index.ts:31:
await $`git --git-dir ${git} --work-tree ${Instance.worktree} add .`No checks exist for:
- Home directory (
~,/home/*,/) - Directory size or file count
- Disk space availability
Suggested fixes
- Block dangerous paths: Skip snapshot if worktree is
$HOME,/home/*, or/ - Size threshold: Warn/skip if directory >1GB or >10k files
- Disk space check: Abort if available disk < 5GB
- User confirmation: Prompt before snapshotting unusually large directories
Activity
github-actions commentedon Jan 15, 2026
This issue might be a duplicate of existing issues. Please check:
Both issues describe the same root cause: the snapshot feature accumulating massive disk space without safeguards. Issue #6845 is an earlier report of the same problem with snapshot consuming extreme amounts of disk space.
Feel free to ignore if your specific case differs from these existing reports.
w32zhong commentedon Mar 9, 2026
We really need snapshot pruning. I am running out of disk space with long running opencode tasks.
piknockyou commentedon Sep 30, 2026
The accidental-
.gitcase in your report is worth a practical footnote for anyone landing here - I hit exactly that condition (a stray empty.gitin the home folder) and it is fixable from the user side without waiting for safeguards:From the folder where you start opencode, run
git rev-parse --show-toplevel..git(rename it if unsure) and start opencode inside an actual project folder; the giant snapshot scan goes away with it.git ls-files --others --exclude-standard | wc -l; if that is very large (100k+), get the heavy folders (node_modules,target, caches) into.gitignore, or set"snapshot": false.Deleting the stray
~/.gitfixed it completely for me - same failure you describe (whole home tracked, disk gone, system unresponsive).