anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Opencode using my 20 GB storage #7533

New Issue
Open
opened 2026-02-16 18:07:28 -05:00 by yindo · 12 comments
yindo commented 2026-02-16 18:07:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @wowiwowe on GitHub (Jan 25, 2026).

Originally assigned to: @rekram1-node on GitHub.

Question

Image

why is my opencode using a lot of storage?

Originally created by @wowiwowe on GitHub (Jan 25, 2026). Originally assigned to: @rekram1-node on GitHub. ### Question <img width="449" height="287" alt="Image" src="https://github.com/user-attachments/assets/c6982b00-3bc1-4868-93a4-6a4207594ebf" /> why is my opencode using a lot of storage?
yindo added the perf label 2026-02-16 18:07:28 -05:00
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 25, 2026):

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

  • #10034: ROOT CAUSE ANALYSIS - tmp_pack Leak causing 137GB-180GB+ disk consumption
  • #10248: Serious memory leak on Windows platform consuming up to 12GB
  • #9851: Taking 10GB while just waiting at step 1 on macOS
  • #10046: Uncontrolled Memory Growth Causing System Overload
  • #10157: Opencode crashes attempting to read too big file

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 25, 2026): This issue might be a duplicate of existing issues. Please check: - #10034: ROOT CAUSE ANALYSIS - tmp_pack Leak causing 137GB-180GB+ disk consumption - #10248: Serious memory leak on Windows platform consuming up to 12GB - #9851: Taking 10GB while just waiting at step 1 on macOS - #10046: Uncontrolled Memory Growth Causing System Overload - #10157: Opencode crashes attempting to read too big file Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@ariane-emory commented on GitHub (Jan 25, 2026):

This is the intended behavior when the snapshot feature is enabled.

You may disable the snapshot feature if you would like to by putting the following in your opencode.json configuration file: "snapshot": false,, but doing so means that the /undo and /redo commands will no longer reverse changes to files as a consequence.

@ariane-emory commented on GitHub (Jan 25, 2026): This is the intended behavior when the snapshot feature is enabled. You may disable the snapshot feature if you would like to by putting the following in your `opencode.json` configuration file: `"snapshot": false,`, but doing so means that the `/undo` and `/redo` commands will no longer reverse changes to files as a consequence.
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Jan 25, 2026):

We auto cleanup snapshots every 7 days, we could make it more frequently

@rekram1-node commented on GitHub (Jan 25, 2026): We auto cleanup snapshots every 7 days, we could make it more frequently
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@ariane-emory commented on GitHub (Jan 25, 2026):

@rekram1-node Neat! I disabled snapshots locally in my own configuration months ago and had not realized that this cleanup feature had been added, I'm going to try re-enabling It immediately and see how much space it ends up taking now. It would be even cooler if the duration for which they were kept could be configured in days.

@ariane-emory commented on GitHub (Jan 25, 2026): @rekram1-node Neat! I disabled snapshots locally in my own configuration months ago and had not realized that this cleanup feature had been added, I'm going to try re-enabling It immediately and see how much space it ends up taking now. It would be even cooler if the duration for which they were kept could be configured in days.
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@cravenceiling commented on GitHub (Jan 25, 2026):

We auto cleanup snapshots every 7 days, we could make it more frequently

Maybe add a config for this?

@cravenceiling commented on GitHub (Jan 25, 2026): > We auto cleanup snapshots every 7 days, we could make it more frequently Maybe add a config for this?
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Jan 25, 2026):

Yeah

@rekram1-node commented on GitHub (Jan 25, 2026): Yeah
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@jsrcode commented on GitHub (Jan 26, 2026):

Yeah

Can you check if https://github.com/anomalyco/opencode/issues/10248 bug no one seems to reply to him

@jsrcode commented on GitHub (Jan 26, 2026): > Yeah Can you check if https://github.com/anomalyco/opencode/issues/10248 bug no one seems to reply to him
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@jsrcode commented on GitHub (Jan 26, 2026):

@rekram1-node* Neat! I disabled snapshots locally in my own configuration months ago and had not realized that this cleanup feature had been added, I'm going to try re-enabling It immediately and see how much space it ends up taking now. It would be even cooler if the duration for which they were kept could be configured in days.

Can you check if https://github.com/anomalyco/opencode/issues/10248 bug no one seems to reply to him

@jsrcode commented on GitHub (Jan 26, 2026): > [@rekram1-node](https://github.com/rekram1-node)* Neat! I disabled snapshots locally in my own configuration months ago and had not realized that this cleanup feature had been added, I'm going to try re-enabling It immediately and see how much space it ends up taking now. It would be even cooler if the duration for which they were kept could be configured in days. Can you check if https://github.com/anomalyco/opencode/issues/10248 bug no one seems to reply to him
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@ariane-emory commented on GitHub (Jan 26, 2026):

@jsrcode Sadly I do not have access to Windows, sorry.

@ariane-emory commented on GitHub (Jan 26, 2026): @jsrcode Sadly I do not have access to Windows, sorry.
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@allanchan339 commented on GitHub (Feb 4, 2026):

This "Git" process snapshot take 30MB/s READ & WRITE respectively, no matter what he is doing it is a performance killer when i am bulk loading data to database

While /redo and /undo take the important role in opencode UX. It is highly recommended to online history cleanup module by session as mentioned in https://github.com/anomalyco/opencode/issues/4980. Not all history deserves redo and undo protection.

@allanchan339 commented on GitHub (Feb 4, 2026): This "Git" process snapshot take 30MB/s READ & WRITE respectively, no matter what he is doing it is a performance killer when i am bulk loading data to database While `/redo` and `/undo` take the important role in opencode UX. It is highly recommended to online history cleanup module by session as mentioned in `https://github.com/anomalyco/opencode/issues/4980`. Not all history deserves redo and undo protection.
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@IM-001 commented on GitHub (Feb 8, 2026):

Ok, the snapshot feature is a must, I cannot work without this. Not sure why specifically today with opus 4.6 it's getting out of control (need to cache 60gb every 10 minutes...).

Also, what's weird is that I had the feeling the cache was growing when agents were simply making search queries in files and codebase, not because of code changes, but I am probably wrong.

However, with swarm agents coming probably eventually, I think it's a must to be able to specify a cache folder on another drive, this can compromise system for users not putting opencode in a sandbox environment. Thank

@IM-001 commented on GitHub (Feb 8, 2026): Ok, the snapshot feature is a must, I cannot work without this. Not sure why specifically today with opus 4.6 it's getting out of control (need to cache 60gb every 10 minutes...). Also, what's weird is that I had the feeling the cache was growing when agents were simply making search queries in files and codebase, not because of code changes, but I am probably wrong. However, with swarm agents coming probably eventually, I think it's a must to be able to specify a cache folder on another drive, this can compromise system for users not putting opencode in a sandbox environment. Thank
yindo commented 2026-02-16 18:07:29 -05:00
Author
Owner
Copy Link
Copy Source

@IM-001 commented on GitHub (Feb 8, 2026):

https://github.com/anomalyco/opencode/issues/12708#issuecomment-3868619680

@IM-001 commented on GitHub (Feb 8, 2026): https://github.com/anomalyco/opencode/issues/12708#issuecomment-3868619680
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label perf
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7533
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?