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
[IMPROVEMENT]: Don't toggle console for non-critical issues #8063
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Recently, I do get console errors and warnings quite frequently, and every time the console window toggles - which impedes my workflow. For non-critical issues, it should be less intrusive, please. A popup "an error occurred, toggle console to report a bug" would be better.
If it's not a crash and I can continue working (95% of cases), I don't want to have to manually toggle the console which overlays my entire screen.
This is consistently happening to me too when I interrupt a task in the middle of a tool call to qwen3-coder-30B-a3b (q5)
[09:50:46] [WARN] 'TSWorker:' 'No parser found for injection language: toml'
....... (multiple repeats of the same line)
[09:50:47] [WARN] 'TSWorker:' 'No parser found for injection language: toml'
[09:53:19] [ERROR] Error: Unexpected end of JSON input
SyntaxError: Unexpected end of JSON input
at <parse> (:0)
at json (unknown)
at <anonymous> (/nix/store/dnw6jy9213ff35pj47s33kys143y8x33-opencode-1.1.
/lib/opencode/dist/src/index.js:178161:43)
at processTicksAndRejections (native:7:39)
Is there a way to dismiss the console without having to exit opencode and start everything again?
Happening a lot for me as well... is there a way to close the console at least?
[08:14:48] [ERROR] Error: Unexpected end of JSON input
SyntaxError: Unexpected end of JSON input
at <parse> (:0)
at json (unknown)
at <anonymous> (../sdk/js/src/v2/gen/client/client.gen.ts:167:33)
at processTicksAndRejections (native:7:39)
I left my MacBook closed all day while opencode was open in the terminal and idle on the welcome screen. When I opened the laptop, I noticed opened console and many errors in the output: [ERROR] Error: The operation timed out.
I’ve also seen the same thing when opencode is left open but unused for a while, especially when the network connection is unstable.
I left my MacBook closed all day while opencode was open in the terminal and idle on the welcome screen. When I opened the laptop, I noticed opened console and many errors in the output: [ERROR] Error: The operation timed out. I’ve also seen the same thing when opencode is left open but unused for a while, especially when the network connection is unstable.
Activity
github-actions commentedon Jan 12, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Jan 12, 2026
Can u provide some examples of what was triggering it? like what u saw?
davetorbeck commentedon Jan 13, 2026
This is also happening to me very frequently
qmx commentedon Jan 13, 2026
This is consistently happening to me too when I interrupt a task in the middle of a tool call to qwen3-coder-30B-a3b (q5)
Is there a way to dismiss the console without having to exit
opencodeand start everything again?sra commentedon Jan 13, 2026
Happening a lot for me as well... is there a way to close the console at least?
davetorbeck commentedon Jan 13, 2026
@qmx @sra As a temp workaround you can close it with
ctrl+pthenToggle Consolebacecek commentedon Jan 13, 2026
I left my MacBook closed all day while
opencodewas open in the terminal and idle on the welcome screen. When I opened the laptop, I noticed opened console and many errors in the output:[ERROR] Error: The operation timed out.I’ve also seen the same thing when
opencodeis left open but unused for a while, especially when the network connection is unstable.jakob1379 commentedon Jan 15, 2026
For me I cannot close the console wiht the
ctrl+ynuppt commentedon Jan 16, 2026
ref:#7883 (comment)
This solution works for me.
github-actions commentedon Mar 26, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.