Snapshot system leaks tmp_pack_* files indefinitely, filling disk at ~9.5 GB/hour

[ChrisMares]

Description

The OpenCode snapshot system creates tmp_pack_* files in the git object store under ~/.local/share/opencode/snapshot//objects/pack/ and never cleans them up. These files accumulate at approximately one new ~9.5 GB file per hour while OpenCode is running, and persist after OpenCode exits. This will silently fill any disk to 100% capacity over time.

Environment

• OS: Ubuntu 24.04, Linux
• Install method: install script

Plugins

No response

OpenCode version

1.2.10

Steps to reproduce

1. Run OpenCode in any project
2. Leave it running for several hours
3. Check ~/.local/share/opencode/snapshot//objects/pack/

Screenshot and/or share link

No response

Operating System

Ubuntu 24.04

Terminal

wezterm

[github-actions]

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

• [BUG] tmp_pack Files Consuming 180GB on Ubuntu 24.04 LTS #8749: [BUG] tmp_pack Files Consuming 180GB on Ubuntu 24.04 LTS
• [BUG] Ubuntu 22.04 Temp_Pack Files Using All of the Storage #5617: [BUG] Ubuntu 22.04 Temp_Pack Files Using All of the Storage
• Opencode using up 380GB in ~/.local/share/opencode/snapshot/objects #9601: Opencode using up 380GB in ~/.local/share/opencode/snapshot/objects
• OpenCode nuked my storage (318 GB added) #9290: OpenCode nuked my storage (318 GB added)
• Opencode using my 20 GB storage #10532: Opencode using my 20 GB storage
• [ROOT CAUSE ANALYSIS] tmp_pack Leak - Complete Code Analysis & Fix Recommendations #10034: [ROOT CAUSE ANALYSIS] tmp_pack Leak - Complete Code Analysis & Fix Recommendations

These issues describe the same tmp_pack file accumulation problem in the snapshot system. Please review them and consider adding your findings there instead, or confirm if your issue represents a distinct case.

[amansingh107]

I think i know why this is happening
1.Failed Snapshots: Every time you interact with the AI, OpenCode tries to snapshot your workspace. If your project is large (or if you accidentally run it in your home directory), these operations can hang.

2.Orphaned Files: When the process hangs or is killed, it leaves those tmp_pack_... files in your .local/share/opencode/.../objects/pack folder.

3.No Auto-Cleanup: The current version of OpenCode (as of early 2026) doesn't have a built-in mechanism to delete these temporary files automatically once they've failed.

[Bewinxed]

Hit this on v1.2.16 — 533GB consumed on a 1.1TB disk (filled to 100%).

Breakdown of the snapshot dir before cleanup:

• Project snapshot (0e0047...): 270GB total — three abandoned tmp_pack_* files (125G + 72G + 72G) plus a corrupted 749M pack file
• global snapshot: 264GB total — one 58G tmp_pack_* file plus ~206GB of loose objects across 258 hash directories (averaging 1.3GB each)
• 5 other snapshots: ~92MB combined (normal)

The loose object accumulation in global seems like a separate-but-related issue — write-tree creates tree objects that stay reachable from the index, so git gc --prune=7.days can't actually prune them. On top of that, when gc does try to repack, it fails (likely OOM or disk pressure) and leaves the tmp_pack_* files behind, compounding the problem.

WSL2 Ubuntu, git 2.43.0. Fix was rm -rf ~/.local/share/opencode/snapshot/* — freed 533GB instantly.

[rothnic]

I just found this issue after hitting 100% disk usage, causing opencode to crash. Found the same snapshot folder taking up 163GB of space for me. What is the solution to handling this safely for now? Between this and the memory leak issues, I'm struggling to use opencode for any length of time without running into performance issues.

I had 120GB if tmp_* files. There are a bunch of pak files that i'm not sure what they are for and the downside of removing them. Most are ~40MB or less, but one is 40GB. Removing the tmp files at least cleaned things up for a bit.