Skip to content

fix(opencode): Terminal event exit completion handling. - #44966

Closed
RadomirMinkov wants to merge 5 commits into
anomalyco:devfrom
RadomirMinkov:bugfix/terminal_events_exit_completion
Closed

RadomirMinkov wants to merge 5 commits into
anomalyco:devfrom
RadomirMinkov:bugfix/terminal_events_exit_completion

Conversation

@RadomirMinkov

@RadomirMinkov RadomirMinkov commented Aug 25, 2026 •

Copy link
Copy Markdown

Issue for this PR

Closes #44901

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

This PR makes opencode run exit normally after the primary session emits a terminal step_finish event with reason: "stop", instead of waitiing indefinitely for a later idle event. It preserves the final JSON event and existing continuation behavior for non-terminal reasons such as unknown.

How did you verify your code works?

The code change was verified with OpenCode’s real subprocess test suite, which launches the CLI as an external process and covers successful JSON runs, continuation after reason: "unknown", attach mode, errors, and signal cleanup. All 13 tests passed, the successful-run test confirmed the final event was step_finish with reason: "stop", and the full package typecheck also passed.

The patched source was then run directly against the same backend used by the Harbor evaluations, without Harbor’s supervisor or forced process termination. It emitted the expected response and terminal step_finish event, then exited naturally with status 0; however, we should not claim that the patched local binary itself was run through Harbor-the earlier Harbor runs tested the wrapper workaround, not this exact upstream patch.

The result from the tests was that a successful model response was received where before that was not the case. The emited termian lstep_finish event with reason: "stop" exited naturally with status 0. These changes make a terminal finish to stop the primary opencode run event loops.

Screenshots / recordings

This is not a UI change, so no screenshot or recordings are needed.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@github-actions github-actions Bot added needs:compliance This means the issue will auto-close after 2 hours. and removed needs:compliance This means the issue will auto-close after 2 hours. labels Aug 25, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for updating your PR! It now meets our contributing guidelines. 👍

@github-actions

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

opencode run --format=json emits terminal step_finish but never exits

1 participant