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
After using opencode for a while (multiple tool calls back and forth), the assistant suddenly stops responding. The UI freezes — no new messages appear, no tool calls execute. The user has to force-close the terminal/app and reopen it to continue. This happens repeatedly in long sessions.
Plugins
No response
OpenCode version
1.17.11
Steps to reproduce
Start a session with opencode
Go through several turns of conversation (edits, builds, git pushes, etc.)
After some time, the assistant goes silent — no response, no loading indicator
Closing and reopening the app is the only fix
Expected behavior: opencode should remain responsive throughout the session.
I might have the same issue on 1.18.31, but I only have this issue on local LLMs. I am using the current latest version of llama.cpp / llama-server built from source as of this date.
This consistently happens after a few minutes of work and I can see from the llama-server logs and from closing opencode and re-opening with --continue that work is still being done while the TUI is no longer responsive
I never have this issue when using models hosted by github copilot and this has been an issue for as long as I have been using opencode, which is a few months
I can see the model is still generating output, etc but opencode is frozen except for the animated thinking and the bouncing ray on the bottom left. Input is written in the field, but no interaction is possible (no menu opens, /exit doesnst work, ctrl+c doesnt work). Only way is to pkill opencode and restart it.
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.
Activity
github-actions commentedon Jun 27, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is the same as one of these, please add a comment there instead so the reports are consolidated.
aryansinghrajput3738-code commentedon Jun 27, 2026
body{
font-family:Arial,sans-serif;
margin:0;
background:#f4f4f4;
}
header{
display:flex;
justify-content:space-between;
padding:20px;
background:#007bff;
color:white;
}
.products{
display:grid;
grid-template-columns:repeat(auto-fit,minmax(220px,1fr));
gap:20px;
padding:20px;
}
.card{
background:white;
padding:15px;
border-radius:10px;
text-align:center;
}
button{
background:#007bff;
color:white;
border:none;
padding:10px 15px;
cursor:pointer;
border-radius:5px;
}
max-wittig commentedon Jul 20, 2026
I can observe the same on macOS with OpenCode Desktop
xinqinglxl commentedon Aug 5, 2026
same problem on macOS TUI 1.17.4, any plan to fix it? any workaround?
Hona commentedon Aug 5, 2026
please try the latest 1.18.13.
1.17 is a very old TUI version.
metareven commentedon Sep 16, 2026
I might have the same issue on 1.18.31, but I only have this issue on local LLMs. I am using the current latest version of llama.cpp / llama-server built from source as of this date.
This consistently happens after a few minutes of work and I can see from the llama-server logs and from closing opencode and re-opening with --continue that work is still being done while the TUI is no longer responsive
I never have this issue when using models hosted by github copilot and this has been an issue for as long as I have been using opencode, which is a few months
laeckerv commentedon Sep 19, 2026
I have the same issue with 1.18.31.
I can see the model is still generating output, etc but opencode is frozen except for the animated thinking and the bouncing ray on the bottom left. Input is written in the field, but no interaction is possible (no menu opens, /exit doesnst work, ctrl+c doesnt work). Only way is to pkill opencode and restart it.
marcelodmdo commentedon Sep 28, 2026
Same here, with 1.18.33 running in WSL2
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊