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
Windows: terminal tool stays in thinking state after dotnet build completes successfully #24926
On Windows, running dotnet build from OpenCode completes successfully, but OpenCode remains stuck in the "thinking" state and never returns the final assistant response. I have to manually kill/restart OpenCode from Task Manager.
The child process appears to finish correctly. The problem seems to be in OpenCode's terminal/tool completion handling rather than in dotnet build itself.
Plugins
No response
OpenCode version
OpenCode Desktop v1.14.29
Steps to reproduce
Open a .NET project in OpenCode Desktop on Windows.
Ask the assistant to run:
powershell dotnet build "sampleproject.csproj"
Build completes and prints successful output.
OpenCode stays in "thinking" state indefinitely.
Manual kill/restart from Task Manager is required.
I tested a workaround that avoids the OpenCode "thinking" hang on Windows.
Instead of running dotnet build directly through the terminal tool, start it as a detached/background process and then read the generated status/log files separately.
This avoids the hang because OpenCode does not wait on the dotnet build child process directly.
Activity
github-actions commentedon Apr 29, 2026
This issue might be related to existing issues. Please check:
tugkan98 commentedon Apr 29, 2026
I tested a workaround that avoids the OpenCode "thinking" hang on Windows.
Instead of running
dotnet builddirectly through the terminal tool, start it as a detached/background process and then read the generated status/log files separately.This avoids the hang because OpenCode does not wait on the
dotnet buildchild process directly.github-actions commentedon Jul 3, 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.