Repository navigation
feat(models): select profile orchestrator explicitly #2214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
decode2
merged 8 commits into
Gentleman-Programming:main
from
NicolasIppoliti:feat/1478-orchestrator-selection
Oct 21, 2026
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
7cdf48f
docs(odd): define explicit orchestrator selection scope
NicolasIppoliti 919d915
feat(models): select profile orchestrator explicitly
NicolasIppoliti 828f4e8
test(models): cover orchestrator choices across panel reopens
NicolasIppoliti 58668e9
docs(odd): record verified orchestrator selection
NicolasIppoliti 2233a7a
docs(odd): record orchestrator selector publication
NicolasIppoliti 84d7ea2
fix(models): preserve target profile orchestrator selection
NicolasIppoliti 827614f
docs(odd): record independent selector correction verification
NicolasIppoliti 1c132c5
test(models): reset session profile bindings after orchestrator panel…
NicolasIppoliti File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Remove the orchestrator key from
restoredbefore the restore writesmodels.json.The new code protects only the panel draft from the export's
orchestratorkey. The write before it (writeModelConfigAsync(ctx.cwd, restored)at Line 3728) persistsrestoredunchanged. An export from a version that still storedorchestratorinmodels.jsontherefore writes that key back into global routing.This conflicts with the change at Lines 3799-3813, which keeps the orchestrator out of
models.json.readEffectiveModelConfigthen returns the stale entry./gentle:profilesbootstrap uses that value, and so dossnapshots when no live model or settings entry overwrites it. In both cases a stale orchestrator can be copied into a profile.Remove the key once before the write. The write,
applyModelConfigAsync, and the draft then all use the same agent-only routing.🐛 Proposed fix
🤖 Prompt for AI Agents