Conversation
A Claude task notification after the parent turn settles cleared background liveness before the follow-up turn started. The thread read as ready in that gap, so the shared completion trigger played the sound, toast, and desktop notification. Mark that completion as resuming the provider and keep liveness working until the follow-up turn starts. Fixes pingdotgg#13625 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
A Claude task notification that arrives after the parent turn has settled now keeps the thread's background liveness as working until the follow-up turn starts. The completion sound, toast, and desktop notification share sidebar status, so none of them fire in that gap.
A completion that does not resume the provider still clears liveness and alerts once. Approvals, questions, and failures still alert immediately.
Why
When a subagent or monitor finished, background liveness cleared before the agent resumed. The thread read as ready with the waiting turn's
completedAt, and the shared completion trigger treated that gap as a finished run. The alert fired, then fired again when the follow-up turn actually settled.The handoff is the task notification with no turn open, and the resume is the next
turn.started. Holding liveness across those two events keeps the shell offreadyfor the whole gap, including while the model is starting the follow-up.Fixes pingdotgg#13625
Checklist