docs: track upstream orchestration V2 and the deferred queue-vs-steer feature - #60
Merged
Merged
Conversation
… feature Sending a message while a turn is running always steers today; there is no queue and no setting. Upstream built queue-with-explicit-steer in pingdotgg#4245, but that PR was closed unmerged on 2026-07-30 in favour of orchestration V2 (pingdotgg#2829), which reportedly has the behaviour natively. Record both halves so the context does not live only in a closed upstream PR: a TODO item to plan the V2 merge, and a FUTURE_ENHANCEMENTS entry explaining why queue-vs-steer is deferred and why the dead branch should not be merged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
size:S
vouch:trusted
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.
Sending a message while a turn is running always steers today — the message is injected into the active turn immediately. There is no queue and no setting. (The
hasQueuedTurnpath inChatComposer.tsxis the offline outbox for a disconnected environment, not this.)Upstream built the queue-with-explicit-steer feature in pingdotgg/t3code#4245 — a server-side per-thread queue, auto-drained on natural turn completion, with per-message Steer and Remove chips above the composer. That PR was closed unmerged on 2026-07-30 in favour of orchestration V2 (#2829), which reportedly has the behaviour natively.
So the whole trail currently lives in a closed upstream PR. This records both halves:
TODO.md— a new "Upstream tracking" item to plan the V2 merge. It replaces the V1 orchestration engine wholesale (810 files, +154k/−74k), so the decider, projector, projection tables, migrations, and every provider adapter are in its blast radius. The weeklysync-upstream.ymlwill surface it the Monday after it lands, most likely as anupstream-sync-blockedissue rather than a clean PR.FUTURE_ENHANCEMENTS.md— a Deferred entry explaining current behaviour, why the deadt3code/queue-steer-featurebranch should not be merged (stale base, colliding migration), and what the cheap fork-local alternative would be if it is wanted sooner.Docs only; no code or behaviour change.
🤖 Generated with Claude Code