You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TUI input frozen when project contains large binary files (project copy refresh hangs) #38201
The TUI becomes unresponsive when opened in a project directory containing large binary files (MP3, WAV, ROM, PNG, etc. — several hundred MB total). The prompt input accepts text but pressing Enter does nothing. The TUI renders correctly (logo, prompt box, status bar) but the input never submits.
Environment
OpenCode version: 1.18.4
OS: Linux (Ubuntu)
Terminal: GNOME Terminal / standard terminal emulator
Steps to reproduce
Create or clone a git repository with large binary assets (e.g. 200+ MB of MP3/WAV/ROM files)
Run opencode in that directory
The TUI displays correctly with the prompt input
Type text in the prompt — text appears normally
Press Enter — nothing happens, the prompt is never submitted
Expected behavior
The prompt should be submitted when pressing Enter, regardless of the project file contents.
Actual behavior
The TUI input is frozen. Pressing Enter has no effect.
Logs
With --log-level DEBUG --print-logs, the last log line is always:
Activity
github-actions commentedon Jul 21, 2026
This issue might be related to existing issues. Please check:
project copy refreshcan block for 48+ seconds (same log boundary:project copy refresh startednever reachingdone)opencode webpermanently hangs (event loop dead, HTTP timeouts) — main thread deadlocks inside@parcel/watchernative subscribe during multi-project attach (Linux) #37111: Event loop deadlock during project attach on Linux (similar symptom of TUI becoming unresponsive due to a blocking operation)These may share the same root cause — the project copy refresh running synchronously or blocking the TUI event loop.
fix(watcher): stop .git-dir subscribe from crawling objects and seria…
github-actions commentedon Sep 20, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.