Confirming this happens on Linux too — consistent ~60-70s pattern #50591

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• Required fields are left as _No response_: OpenCode version, Steps to reproduce, Operating System, and Terminal. Please fill these in — version and OS in particular are essential for triaging this class of bug.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

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

• Session permanently frozen: drain() failures are logged but never surfaced to the client (no session.error event) #49740: Session permanently frozen — drain() failures logged but never surfaced to the client (same symptoms: silent stall after ~60s, no error in TUI, opencode-auto-resume plugin failing to load on v2.0.x described as corroborating evidence)
• "opencode run": zero-chunk provider stream stall never surfaces — no timeout, no retry, no exit (1.18.30) #48675: Zero-chunk provider stream stall never surfaces — no timeout, no retry (same "stream goes silent, session freezes" pattern)

If you believe this was flagged incorrectly, please let a maintainer know.

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.

Had the same failure: the session title gets created, but no reply ever comes - only the server restarted while you were working notice, with event stream disconnected / stalled in the log.

Root cause for me: a stray empty .git folder in my home folder. That hidden folder makes everything around it look like one big "git project" - so opencode treated my entire home folder as the project and scanned all of it for changes before each reply (541k files, ~26 seconds per scan, twice per message). That is longer than opencode's internal watchdog waits, so it assumes the service died, restarts it, and you get the loop.

Quick check - run this in the folder where you start opencode:

git rev-parse --show-toplevel

• If it prints your home folder (or a big folder above the project you actually work in), that leftover .git is the problem. Delete that .git folder (accidents like this usually contain no commits, so nothing is lost - if unsure, just rename it to .git.bak). Then start opencode inside a normal project folder, and never run git init in your home folder. This removed the failure completely for me.
• If it prints your real project folder, the folder is fine and the files inside are the problem. Run:
  git ls-files --others --exclude-standard | wc -l
  If that number is huge (100k+), opencode is choking on files that should have been skipped. List your big folders that don't belong to the project (node_modules/, target/, build/, caches, datasets) in a .gitignore file - one per line. As a last resort you can set "snapshot": false in your opencode config, which switches the scan off (but you also lose the undo feature).

Deleting the stray ~/.git / %USERPROFILE%\.git was enough for me.