[Fix] Task Info preserves each task's inference provider#436
Merged
Conversation
Contributor
Author
|
All issues addressed. See task
|
Contributor
Author
|
Fixed in b36e390: fresh tasks now persist the resolved provider at launch, and Task Info uses that immutable snapshot. Legacy |
mrubens
marked this pull request as ready for review
July 16, 2026 18:00
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 16, 2026 18:00
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.
What changed
Tasks now snapshot their resolved inference provider at launch. Task Info reads that immutable snapshot, so ChatGPT subscription-backed tasks remain labeled
ChatGPT (subscription)even if deployment credentials later change.The sidebar retains model-prefix labels for legacy tasks recorded with the former generic
opencodeprovider value.Why this change was made
The previous implementation inferred the label from the deployment's current ChatGPT connection state, which could relabel historical tasks incorrectly after a provider connection changed.
Impact
Task Info accurately reflects the provider used for new tasks across later configuration changes, while preserving sensible labels for existing tasks.