Conversation
OpenCode background subagents stay busy after the parent turn settles, but they never emit task events, so the reaper treated the thread as idle and stopped the provider session. Related child session.status is now quiet liveness for that reaper check. The tracker is an Effect service built with the runtime, so each runtime has its own map. busy and retry hold the session; idle, deletion, and teardown release it. The signal stays inside the reaper and leaves task activity unchanged. Fixes pingdotgg#13514
github-actions
Bot
added
vouch:trusted
Owner
Author
|
Opened upstream. |
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
1 participant
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.statusis quiet liveness for the provider-session reaper. The tracker is an Effect service (OpenCodeChildSessionLiveness) provided once per server runtime. The OpenCode adapter and the reaper bothyield*that service.busyandretryhold that thread's binding.idle, deletion, and session teardown release the child. While any related child is still live, an inactivity sweep leaves the OpenCode session running and does not move the idle clock. The next sweep can reap once the last child is gone. Other providers are unchanged.The map lives in the service instance for that runtime. A second runtime, test, or isolated layer cannot see another runtime's holds.
Why
Fixes pingdotgg#13514
On a headless OpenCode session, long-running background subagents keep the provider process busy after the parent turn settles. They do not emit
task.*events, so the reaper treated that silence as inactivity and stopped the session withinactivity_threshold, which cancels the tracked children.The hold stays inside the reaper. Task activity is unchanged, so the sidebar liveness pill, thread settlement, and storage cleanup keep their existing task-event behavior.
Checklist