Repository navigation
Conversation
…gents still run Claude's terminal takes a message once its turn is over, with subagents still out. The queue only sent on finished, so a reply queued mid-turn sat until every background agent was done. The runner now reads the log's turn ending and sends then; replies from Decisions, the palette and menus read it too, so they go straight in. A batch's next step still waits out the agents. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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.
From the marked moment 2026-11-16T16-35-43-276Z: "it doesnt handle queueing right when we have background agents running. we want all the claude terminal features captured".
What was wrong. A reply queued while a thread was mid-turn waited until every background agent was done ("Queued, sent when its agents finish"). In that moment the turn ended at 16:35:33 with a builder still working, so the reply would have waited out a 20+ minute build. Claude's terminal takes a message as soon as the turn ends. The queue runner only sent on
finishedand never read the log's turn ending. Replies from Decisions, the palette and menus didn't passturnEndedAteither, so a thread held for its subagents always queued them.Now
thread_transcript, cheap because Rust reads on from where it was) and sends the next reply once the turn is over, even with subagents still out (holdNext(…, turnEndedAt)).enqueuereads it too when the caller didn't pass it, so Decisions, palette and menu replies to a held thread go straight in.afterAgentsand still waits for the agents. This keeps Keep talking to a thread from the Read view while its subagents work #148's caution where it applies.afterAgentsstep.tests/fixtures/moments/2026-11-16T16-35-43-276Z.jsonchecks the moment. The Keep talking to a thread from the Read view while its subagents work #148 fixture gainsholdReply: null.scripts/fake-agent.shgains abackgroundturn: it works for 15s, sends a builder off and logs its turn end.Not checked live. The Mac sandbox's daemon is a stale one from the removed
idle-cpuworktree (its fake agent and demo repos are gone), and auto mode blocked stopping it. The PC needs a Tailscale re-auth. Draft until it's been seen in the sandbox:background goin a thread, queue a reply during the 15s, and the reply should go in about 5s after "a builder is working in the background."Checks:
npm run build && npm testpass (636). No Rust changes.🤖 Generated with Claude Code