Repository navigation
feat(fork): answer earlier Chat-mode messages in sub-threads - #250
Merged
Merged
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
orbitingflea
force-pushed
the
feat/chat-steer-reply-in-thread
branch
from
November 22, 2026 03:27
622c4e2 to
5bab5d3
Compare
When the user sends a second main-list message while the agent is still on the first, the agent may now answer the first one separately. That answer shows in the first message's sub-thread; answers to the latest main-list message still show in the main list. - foldCores places an answer to a main-list message in that message's sub-thread when a later main-list user message comes before it. - send_to_user no longer refuses such an answer. It refuses once when a later main-list message is a steer that no provider has confirmed reading (pending, cancelled, or never past the time it was stored), and lists it; the retry goes through. - The result text, the Chat mode rules (chat-replies@4), the per-message line and the reply_to description state the new placement, with same-topic versus separate-topic guidance. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
orbitingflea
force-pushed
the
feat/chat-steer-reply-in-thread
branch
from
November 22, 2026 08:27
5bab5d3 to
cad9781
Compare
This was referenced Nov 22, 2026
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.
This pull request lets Chat-mode agents answer an earlier main-list message in its sub-thread.
改了什么行为
Behaviour change: yes, web and desktop Chat-mode users see answers to earlier main-list messages in sub-threads.
Before,
send_to_userrefused answers to earlier main-list messages. Now an answer to the latest message stays in the main list, and a separate answer to an earlier one shows in its sub-thread under a reply line ("1 reply"). If a later mid-turn message is not yet confirmed as read, the first call to answer an earlier one is refused once and returns it in full.Why
Users sometimes send two separate questions in a row in Chat mode. Putting the earlier answer in its sub-thread keeps each answer under its question and the main list ordered.
Checks
send_to_user,replace_send_to_user, user view, and web summary;vp run check:changedpasses.How to undo
Revert the commit; no stored data changes, and existing threads get the old rules again when the rules version reverts.
Details
Behaviour details:
send_to_userresult states where the answer went ("in that message's sub-thread, because the user wrote later in the main list") and lists unanswered user messages.replace_send_to_useredits that answer in place until the user replies after it in that sub-thread.How it works:
foldCores) puts an answer to a main-list message in its sub-thread when a later main-list user message precedes it. The web timeline, server tools, user view (t3_thread_user_view), and history loader all usefoldCores, so they agree.send_to_userfolds its history plus the new answer throughfoldCoresto report placement and list unanswered user messages.isUnread, beside the reply-stage judge) and the agent's answers or acknowledgements to the later message. Pending, cancelled, or never-confirmed mid-turn messages refuse at most once via an in-memory server record kept for 10 minutes.Accepted tradeoffs:
Surfaces not changed:
Upstream hooks:
apps/server/src/provider/agentContextBudget.json(+1/-1 line) grows the measured tool-list size by 115 bytes for the longerreply_todescription.