Snapshots: a large untracked file is kept forever by the op log; expire snapshots, and guard big files issue #98 closed: completed andymccall opened this 24 days ago · 0 comments

From oxygen_feedback.md (Metal Gear, 2026-10-11): a 1 GB Docker tarball, untracked and not yet ignored, was taken in by a working-copy snapshot when the editor ran status. It was never committed or pushed and no bookmark holds it, yet gc keeps it (about 380 MB of packs) because the op log's snapshots reach it, and nothing expires them. Asks: a way to expire working-copy snapshots older than a time, or forget an operation (oxy op forget OP), so gc can prune what only they held; and a size guard: an untracked file over a limit (say 100 MiB) is not snapshotted without a word, but skipped and named, with how to add it on purpose.