anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Running killall node causes broken state #2578

New Issue
Closed
opened 2026-02-16 17:36:19 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 17:36:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @Irrelon on GitHub (Nov 4, 2025).

Description

When running opencode with an open session but no active prompt running, running killall node then attempting to use a prompt will cause a "queued" state to appear rather than executing the prompt.

Doing a double CMD+c to kill the process then opening again and going to that session shows the prompt as processing but it never changes or gets sent to the remote LLM provider.

Double-tapping esc does not fix the problem or cancel the prompt. The session becomes broken and cannot be resumed.

OpenCode version

0.6.5

Steps to reproduce

  1. Prompt inside opencode to create a session
  2. After the prompt has completed, go to shell and run killall node
  3. Attempt to prompt
  4. Session is now in a broken state and cannot be resumed or used further

Screenshot and/or share link

No response

Operating System

MacOS 15.6

Terminal

Ghostty

Originally created by @Irrelon on GitHub (Nov 4, 2025). ### Description When running opencode with an open session but no active prompt running, running `killall node` then attempting to use a prompt will cause a "queued" state to appear rather than executing the prompt. Doing a double CMD+c to kill the process then opening again and going to that session shows the prompt as processing but it never changes or gets sent to the remote LLM provider. Double-tapping `esc` does not fix the problem or cancel the prompt. The session becomes broken and cannot be resumed. ### OpenCode version 0.6.5 ### Steps to reproduce 1. Prompt inside opencode to create a session 2. After the prompt has completed, go to shell and run `killall node` 3. Attempt to prompt 4. Session is now in a broken state and cannot be resumed or used further ### Screenshot and/or share link _No response_ ### Operating System MacOS 15.6 ### Terminal Ghostty
yindo added the bug label 2026-02-16 17:36:19 -05:00
yindo closed this issue 2026-02-16 17:36:19 -05:00
yindo commented 2026-02-16 17:36:19 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Nov 4, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #390: session broken after hitting "esc" in the middle of tool use - Similar broken session state that cannot be recovered
  • #2783: Idea: use ZeroMQ or WebSockets for shared event bus, synchronize multiple opencode TUIs and servers - Mentions broken state when multiple processes access sessions
  • #2046: Error: Failed To Open Session - Session fails to open after killing process
  • #3846: No response to user input - Session becomes unresponsive and requires killing the process
  • #2380: bug: immediately exits and other processes never exit - Issues with process management and killing opencode processes

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Nov 4, 2025): This issue might be a duplicate of existing issues. Please check: - #390: session broken after hitting "esc" in the middle of tool use - Similar broken session state that cannot be recovered - #2783: Idea: use ZeroMQ or WebSockets for shared event bus, synchronize multiple opencode TUIs and servers - Mentions broken state when multiple processes access sessions - #2046: Error: Failed To Open Session - Session fails to open after killing process - #3846: No response to user input - Session becomes unresponsive and requires killing the process - #2380: bug: immediately exits and other processes never exit - Issues with process management and killing opencode processes Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:36:19 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 4, 2025):

@Irrelon btw you are on an ancient version of opencode

@rekram1-node commented on GitHub (Nov 4, 2025): @Irrelon btw you are on an ancient version of opencode
yindo commented 2026-02-16 17:36:19 -05:00
Author
Owner
Copy Link
Copy Source

@Irrelon commented on GitHub (Nov 4, 2025):

@Irrelon btw you are on an ancient version of opencode

Thanks for the heads up. I'll upgrade and re-confirm, or close if no longer replicating.... doing a brew upgrade opencode right now...

@Irrelon commented on GitHub (Nov 4, 2025): > [@Irrelon](https://github.com/Irrelon) btw you are on an ancient version of opencode Thanks for the heads up. I'll upgrade and re-confirm, or close if no longer replicating.... doing a `brew upgrade opencode` right now...
yindo commented 2026-02-16 17:36:19 -05:00
Author
Owner
Copy Link
Copy Source

@Irrelon commented on GitHub (Nov 4, 2025):

Actually, I'll close and re-open if I continue to experience the issue. :)

@Irrelon commented on GitHub (Nov 4, 2025): Actually, I'll close and re-open if I continue to experience the issue. :)
yindo commented 2026-02-16 17:36:19 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 4, 2025):

sweet!

@rekram1-node commented on GitHub (Nov 4, 2025): sweet!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2578
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?