opencode is stuck in the chromium source code directory #30386

Activity

1. github-actions commented on Jun 2, 2026

   

   github-actionsBot

   on Jun 2, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Snapshot git add runs indefinitely on worktrees with large non-code files #18072: Snapshot git add runs indefinitely on worktrees with large non-code files (same root cause — opencode's snapshot system running git operations on large directories)
   • Why is OpenCode massively abusing git? #3176: OpenCode massively abusing git (general issue with git snapshot behavior on large directories)
   • Work very slowly in large git repos(2GB+) #12437: Work very slowly in large git repos (2GB+)

   The Chromium source tree is extremely large, so opencode's snapshot system is likely triggering long-running git operations. You may be able to work around this in the meantime by disabling snapshots in your config.
2. github-actions

   assigned

   StarpTech

   on Jun 2, 2026
3. github-actions commented on Aug 2, 2026

   

   github-actionsBot

   on Aug 2, 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.
4. github-actions

   closed this as not plannedon Aug 2, 2026
5. piknockyou commented on Sep 30, 2026

   

   piknockyou

   on Sep 30, 2026

   More actions

   Same symptom here on a very large checkout - no response for a long time while git churns. One diagnostic step before disabling snapshots outright, from the folder where you start opencode:

   git rev-parse --show-toplevel

   • If it prints something far above the checkout (a parent folder with a stray git init, or your home folder): delete that leftover .git (usually empty; rename if unsure) and start opencode inside the real project folder - that removes the giant scan entirely.
   • If it prints the chromium checkout itself (likely): the snapshot walk is enumerating your build output and caches. Check git ls-files --others --exclude-standard | wc -l; if it is huge, get the heavy directories (out/, node_modules, caches) into .gitignore - that is the same tree the snapshot walks - or set "snapshot": false if you do not need undo there.

   Shrinking that scan set was the difference for me between "stuck for minutes per step" and normal speed.