Conversation
OpenCode background subagents stay busy after the parent turn settles, but they never emit task lifecycle events. The reaper therefore treats the thread as idle and stops the provider session. Related child session.status of busy or retry now records a live task, and idle clears it. The existing background-liveness guard skips the reap while that work is running. Fixes pingdotgg#13514 Co-authored-by: maco <macodev00@users.noreply.github.com>
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
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.
What Changed
Related OpenCode child
session.statusnow feeds the existing background-liveness registry.busyandretryrecord a live task;idleclears that child. The session reaper is unchanged and already skips a thread whilebackgroundLivenessis set.Why
Fixes pingdotgg#13514
On a headless OpenCode session, long-running background subagents keep the provider busy after the parent turn settles, but they never emit
task.*events. The reaper measured only user-facing activity and stopped the session withinactivity_threshold, aborting in-flight work. Child status is the signal that this work is still live. Completion notifications on the parent do not move the idle clock, so they are not used.Checklist
No UI changes.