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
Opencode Stops Processing Requests Without Response #32149
I would like to report an issue that I am currently experiencing with Opencode.
Issue Description:
Whenever I submit a new prompt or request in Opencode, the application starts processing and displays the "thinking" state for a few moments. However, instead of generating a response, it automatically stops and plays the stop/completion sound without providing any output or error message.
Steps to Reproduce:
Open Opencode.
Enter any new prompt or request.
Submit the prompt.
Opencode begins thinking for a short period.
The process automatically stops, accompanied by the completion sound, but no response is generated.
Troubleshooting Steps Already Attempted:
Reinstalled Opencode completely.
Re-entered and verified my Opencode API key.
Restarted the application after reinstalling.
Unfortunately, the issue persists despite these attempts.
Please investigate this issue and advise on any additional troubleshooting steps or a potential fix. If logs or diagnostic information are required, I would be happy to provide them.
Thank you for your assistance. I look forward to your response.
Plugins
No response
OpenCode version
v1.17.4
Steps to reproduce
Open "OpenCode" Desktop
Go to any existing workspace or a new one
Open a new chat/session
Submit a request
Experience the bug; it won't do anything.
Screenshot and/or share link
No response
Operating System
macOS Monterey 12.x (Late 2015 iMac)
Terminal
iTerm2, Default MacOS Terminal
Reacted by Ding, ModernCreator068, anuoua, スコット, Anurag Mishra, joemama, Kristófer Helgi Sigurðsson, pdfrg, John Leonardo, nico and 3 more
If your issue is the same, please add a "+1" reaction or comment on those issues rather than opening a new one. This helps maintainers track the scope of a problem more effectively.
Reacted by aliyancat, okasi, philippgrubitzsch, Anas and BatuKvi123
Experiencing the same issue on Laptop B but not Laptop A, despite both being set-up exactly the same, running the same versions. Additionally, issue does not seem to be OS-specific, as I'm running Windows (10 & 11).
Also, both: #32400 and #32606 seems to have the exact same problem.
Unlike user Tonoman3g, there is no error response. Just the "Thinking..." for a second or so and a "Task done" sound.
I spent one whole day to understand what is happening and the real problem was that opencode is reading stale directory paths. I fixed in my machine by:
run opencode web command.
In the UI dashboard, on left hand side you will find the projects part. Clean it up.
Then add a new project because currently what I found is that opencode do not work without attaching a project.
Then create a new session and start working on that project.
I ran some debugging on the codebase and I was repeatedly getting NOTFOUND error.
I spent one whole day to understand what is happening and the real problem was that opencode is reading stale directory paths. I fixed in my machine by:
run opencode web command.
In the UI dashboard, on left hand side you will find the projects part. Clean it up.
Then add a new project because currently what I found is that opencode do not work without attaching a project.
Then create a new session and start working on that project.
I ran some debugging on the codebase and I was repeatedly getting NOTFOUND error.
But one this is sure that the current directory selector in UI is really bad.
I can confirm that it works. If we open the project on the web, sending messages to same project on the desktop will work.
Unfortunately the projects picker on the web is really bad, I can only search projects one level deep from the home directory. Also it means that I have to reopen every project to fix the issue.
I have a similar issue. Version: 1.18.20, OS Ubuntu 24.04, TUI. The process suddenly stops at random times during the thinking/edit/reply step. It resumes after the "Continue" message. I've observed this error with all free models: Big Pickle, Deepseek, MiMo, etc.
it's honestly so bad. I can't even get any prompt to finish. I just have to keep re-submitting and hoping for one to actually complete. wasting time, wasting tokens, it's a mess. this is on Go. doesn't matter the model.
Got the same situation started happening just today. Big pickle model is processing the task, then issues a cmd which prints: <invoke ...>...</invoke>
and just stops processing completely/goes idle. Happens every 20s now. Unable to use it/work with.
Same symptom here - thinking for a moment, then stopping without a reply. One of the comments here already suspected this to be project- or git-related, and that matches my experience, so here is the concrete version of that check.
For me the cause was a stray empty .git in my home folder - opencode ran from home, treated the whole home tree as one project, and the snapshot scan before/after each step crawled it (500k+ files, ~26s per scan) until the service kept getting killed and restarted.
From the folder where you start opencode: git rev-parse --show-toplevel
Prints your home folder (or a big parent folder) instead of your project -> delete that leftover .git (usually empty, nothing lost; rename if unsure) and start opencode inside a real project folder.
Prints your real project -> git ls-files --others --exclude-standard | wc -l; if that is 100k+, put the heavy folders (node_modules, target, caches) into .gitignore or set "snapshot": false.
Deleting the stray .git removed the failure completely for me. If neither applies, ignore this.
Thanks for the detailed report, and sorry for the trouble.
You're on v1.17.4, which is OpenCode v1. v1 now only gets fixes for critical problems such as data loss, security issues or crashes with no workaround, so this one is unlikely to be fixed there.
Things worth trying:
Upgrade to OpenCode v2 (npm package @opencode/cli, command opencode). v2 is a separate implementation, and that's where active work happens.
Try a different model or provider to see whether the empty replies only happen with one model.
These issues describe a similar symptom (a turn that finishes with no visible output). As far as I can tell they're about v2, so they're only related:
If this also happens on v2, or you think it's critical, please reply with your v2 version (opencode --version), the provider and model you're using, and any logs.
Also, this is a public issue, so you may want to edit it and remove your email address. For anything about your Go subscription or account, email help@anoma.ly.
Closing this as not planned. It was reported on OpenCode v1 (v1.17.4), which now only gets fixes for critical problems, and there hasn't been an update since.
If you see the same empty replies on OpenCode v2 (@opencode/cli), please open a new issue. Include the output of opencode --version, the provider and model you're using, and any logs. For anything about your Go subscription or account, email help@anoma.ly. Thanks for reporting this!
Activity
github-actions commentedon Jun 13, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is the same, please add a "+1" reaction or comment on those issues rather than opening a new one. This helps maintainers track the scope of a problem more effectively.
tonoman3g commentedon Jun 13, 2026
i also had this kind of issue.
it stopped working, and then sending another message shows this error
VitalyM commentedon Jun 13, 2026
try to change effort, maybe this helps: #25793 (comment)
TimChinye commentedon Jun 24, 2026
Experiencing the same issue on Laptop B but not Laptop A, despite both being set-up exactly the same, running the same versions. Additionally, issue does not seem to be OS-specific, as I'm running Windows (10 & 11).
Also, both: #32400 and #32606 seems to have the exact same problem.
Unlike user Tonoman3g, there is no error response. Just the "Thinking..." for a second or so and a "Task done" sound.
TimChinye commentedon Jun 24, 2026
I suspect the issue to be project-specific and git-related.
jeremyakers commentedon Jun 26, 2026
I'm having the same issue for weeks.
anuoua commentedon Jul 2, 2026
I have this problem, sometimes break without error message.
jsaunders92 commentedon Jul 28, 2026
Same issue happening here too.
fdarian commentedon Aug 2, 2026
+1 on this
eacryo commentedon Aug 11, 2026
I also have same issue,v1.18.16 still not solved
Anujanthwal-dotcom commentedon Aug 17, 2026
I want to work on this issue if someone else is not working on it. I see @Hona is assign to this issue but the issue is not fixed yet.
Anujanthwal-dotcom commentedon Aug 18, 2026
I am not getting any reply on my previous message so I will be opening a PR directly. Hope that works for all.
Anujanthwal-dotcom commentedon Aug 18, 2026
I spent one whole day to understand what is happening and the real problem was that opencode is reading stale directory paths. I fixed in my machine by:
I ran some debugging on the codebase and I was repeatedly getting NOTFOUND error.
File: packages/opencode/src/server/routes/instances/httpapi/handlers/session.ts
function: promptAsync
But one this is sure that the current directory selector in UI is really bad.
Anujanthwal-dotcom commentedon Aug 18, 2026
I have tested opencode web command multiple times after this and it works. But I will still check it further.
fdarian commentedon Aug 18, 2026
I can confirm that it works. If we open the project on the web, sending messages to same project on the desktop will work.
Unfortunately the projects picker on the web is really bad, I can only search projects one level deep from the home directory. Also it means that I have to reopen every project to fix the issue.
daniilpanov commentedon Aug 21, 2026
I have a similar issue. Version: 1.18.20, OS Ubuntu 24.04, TUI. The process suddenly stops at random times during the thinking/edit/reply step. It resumes after the "Continue" message. I've observed this error with all free models: Big Pickle, Deepseek, MiMo, etc.
pdfrg commentedon Aug 22, 2026
it's honestly so bad. I can't even get any prompt to finish. I just have to keep re-submitting and hoping for one to actually complete. wasting time, wasting tokens, it's a mess. this is on Go. doesn't matter the model.
daniilpanov commentedon Aug 23, 2026
I think we should mark this issue as a bug.
fabiangerhardt-star commentedon Aug 24, 2026
I have the same issue on macOS app. Did someone already TS and found the root cause?
fidodido48 commentedon Aug 28, 2026
Got the same situation started happening just today.
Big pickle model is processing the task, then issues a cmd which prints:
<invoke ...>...</invoke>and just stops processing completely/goes idle. Happens every 20s now. Unable to use it/work with.
piknockyou commentedon Sep 30, 2026
Same symptom here - thinking for a moment, then stopping without a reply. One of the comments here already suspected this to be project- or git-related, and that matches my experience, so here is the concrete version of that check.
For me the cause was a stray empty
.gitin my home folder - opencode ran from home, treated the whole home tree as one project, and the snapshot scan before/after each step crawled it (500k+ files, ~26s per scan) until the service kept getting killed and restarted.From the folder where you start opencode:
git rev-parse --show-toplevel.git(usually empty, nothing lost; rename if unsure) and start opencode inside a real project folder.git ls-files --others --exclude-standard | wc -l; if that is 100k+, put the heavy folders (node_modules,target, caches) into.gitignoreor set"snapshot": false.Deleting the stray
.gitremoved the failure completely for me. If neither applies, ignore this.opencodejr commentedon Oct 29, 2026
Thanks for the detailed report, and sorry for the trouble.
You're on v1.17.4, which is OpenCode v1. v1 now only gets fixes for critical problems such as data loss, security issues or crashes with no workaround, so this one is unlikely to be fixed there.
Things worth trying:
@opencode/cli, commandopencode). v2 is a separate implementation, and that's where active work happens.These issues describe a similar symptom (a turn that finishes with no visible output). As far as I can tell they're about v2, so they're only related:
If this also happens on v2, or you think it's critical, please reply with your v2 version (
opencode --version), the provider and model you're using, and any logs.Also, this is a public issue, so you may want to edit it and remove your email address. For anything about your Go subscription or account, email help@anoma.ly.
opencodejr commentedon Oct 30, 2026
Closing this as not planned. It was reported on OpenCode v1 (v1.17.4), which now only gets fixes for critical problems, and there hasn't been an update since.
If you see the same empty replies on OpenCode v2 (
@opencode/cli), please open a new issue. Include the output ofopencode --version, the provider and model you're using, and any logs. For anything about your Go subscription or account, email help@anoma.ly. Thanks for reporting this!