Conversation
…case screenshots (pingdotgg#13316) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: t3-code[bot] <269035359+t3-code[bot]@users.noreply.github.com> Co-authored-by: Exotic <118054752+extoci@users.noreply.github.com>
…otgg#11580) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Simone <185146821+Lucenx9@users.noreply.github.com>
…3355) Co-authored-by: Yordis Prieto <yordis.prieto@gmail.com> Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
Queued messages only left from the selected chat view, so a follow-up sent while a turn was still running waited until that thread was opened again. A coordinator now sends due follow-ups for threads that are not on screen. Implemented with Grok 4.7 in Cursor. Co-authored-by: maco <macodev00@users.noreply.github.com>
github-actions
Bot
added
vouch:trusted
|
@coderabbitai review |
Owner
Author
|
Superseded by upstream READY (same head). |
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
9 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.
What Changed
Queued follow-ups are dispatched for threads that are not currently open. The selected thread still sends through the chat view.
Why
Fixes pingdotgg#13319.
With follow-up behavior set to Queue, a message sent during a running turn stays in the in-memory queue. The effect that later sends it lives in
ChatViewand only watches the selected thread. Switching threads, or leaving the chat layout, stops that effect. The follow-up is sent when the thread is opened again, so the working-time counter starts near zero on return.Hunch, consistent with the maintainer note on the issue: the multi-minute wait is before
thread.turn.start, not a stale timer. An idle-thread send already goes out immediately and does not need the thread to stay selected.The coordinator subscribes to threads that have a queue, including while Settings is open, and sends at the same tool and turn boundaries. Stop cancels an in-flight background send. A failed send is held for retry instead of looping. Native mobile keeps its own queue.
UI Changes
No visual change. A queued follow-up now starts while you are in another thread, so returning shows the elapsed working time.
Checklist