Repository navigation
fix(server): thread-bound scheduled tasks run on the thread's current provider - #13
Merged
Merged
Conversation
… provider Port of upstream a27e32f (pingdotgg#18467). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
added
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
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.
Upstream fix a27e32fba7 — thread-bound scheduled tasks run on the thread's current provider (pingdotgg/t3code#18467)
Existing systems changed
ScheduledTaskService: a run of a thread-bound scheduled task no longer passes the task's stored
modelSelectiontoThreadManagementService.sendToThread. The send therefore uses the thread's current model selection, assendToThreadalready does when no selection is given (the same path the MCPt3_thread_sendtool uses).The stored selection now only seeds fresh threads (tasks without a bound thread still launch with it). Before, every automated run in a thread whose provider had changed since the task was created switched the thread to the task's provider and back.
How the systems interact
mode: "queue".Verifiable outcome
Upstream PR pingdotgg/t3code#18467 with its regression test
🤖 Generated with Claude Code