[codex] Persist custom model selection#100
Merged
Cyberforker merged 1 commit intoJun 15, 2026
Merged
Conversation
Collaborator
Review SummaryReviewed & merged by Carbon Code Tests: npm run verify - 3918/3918 passed, 2 skipped Thanks @Star-Star66 for the thorough model-persistence implementation and coverage across entry points. Co-Authored-By: Carbon Code carboncode@code.ai6666.com -- Carbon Code |
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.
Summary
/modelselections in~/.carboncode/config.json--model> saved model > preset defaultWhy
Selecting a model that is not one of the built-in flash/pro presets only changed the current process. After restarting Carbon Code, the CLI silently returned to the preset model. This was especially confusing for custom or OpenAI-compatible model IDs.
This change preserves the user's explicit model choice across restarts without expanding the scope into full multi-provider configuration. Existing configs remain compatible because the new
modelfield is optional.Validation
npm run verify