Handle OpenCode process exit events and prevent hanging - #8
Merged
Conversation
The handleAsk promise in chatParticipant only listened for "done" and
"error" events from bridge.onEvent. When the OpenCode process exited
cleanly (code 0 or null), handleExit only called setState("stopped")
without firing any event, so the promise never resolved and the UI
hung indefinitely.
Two fixes:
- opencodeBridge: fire an error event in handleExit for clean exits so
listeners are always notified when the process ends
- chatParticipant: add an onStateChanged listener as a safety net so
the promise resolves even if a state change fires without an event
https://claude.ai/code/session_01H4amgmKjeCoRweW1fK9PDc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds proper handling for OpenCode process exit events to prevent chat responses from hanging indefinitely when the process terminates unexpectedly.
Key Changes
opencodeBridge.tsthat fires an error event when the process exits with code 0 or null (unexpected clean exit), and transitions to "error" state for non-zero exit codeschatParticipant.tsthat resolves the chat promise if the bridge stops or errors without emitting an event (e.g., process killed externally)Implementation Details
https://claude.ai/code/session_01H4amgmKjeCoRweW1fK9PDc