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
OpenCode becomes completely unresponsive when running in WSL2. The freezing starts immediately on launch and follows a consistent pattern: 5-10 seconds frozen, then 5-10 seconds responsive, repeating indefinitely. This affects all operations including typing (characters freeze then appear all at once), LLM streaming output, scrolling, and even idle state.
Both Claude Code and Gemini CLI work flawlessly in the exact same WSL2 environment,
Switching terminals from Windows Terminal to WezTerm made no difference.
The issue persists regardless of shell choice or project complexity.
All three issues describe periodic freezing/lag on WSL2 with similar symptoms (buffered input appearing after freeze, consistent 5-10 second intervals). These are known WSL2-specific issues.
Feel free to ignore if your specific case differs from these.
There's apparently some memory not being released issue I've read about and while it might be the potato I'm running on right now running, whether via a Ralph harness or in TUI it will often hang especially with tool calls like doing a bash run cmake compile script.
Resolved! Found the solution in #8484 thanks to @pschiel's comment: #8484 (comment) Cause:systemd-timesyncd in WSL2 causes time sync conflicts with Windows/Hyper-V, resulting in corrupted timestamps that freeze JavaScript timeouts. Solution:
Activity
github-actions commentedon Jan 31, 2026
This issue might be a duplicate of existing issues. Please check:
All three issues describe periodic freezing/lag on WSL2 with similar symptoms (buffered input appearing after freeze, consistent 5-10 second intervals). These are known WSL2-specific issues.
Feel free to ignore if your specific case differs from these.
Nsomnia commentedon Feb 1, 2026
There's apparently some memory not being released issue I've read about and while it might be the potato I'm running on right now running, whether via a Ralph harness or in TUI it will often hang especially with tool calls like doing a bash run cmake compile script.
gabrielsoda commentedon Feb 1, 2026
Resolved! Found the solution in #8484 thanks to @pschiel's comment:
#8484 (comment)
Cause:
systemd-timesyncdin WSL2 causes time sync conflicts with Windows/Hyper-V, resulting in corrupted timestamps that freeze JavaScript timeouts.Solution:
sudo systemctl disable systemd-timesyncd && sudo systemctl stop systemd-timesyncdThis completely fixed the input lag and freezing for me. Closing as resolved.