-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Conversation
Open
@Star-Star66
Star-Star66
force-pushed
the
codex/issue-95-config-hot-reload
branch
from
June 13, 2026 02:55
5c2ebb3 to
ae2e6e2
Compare
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.
Uh oh!
There was an error while loading. Please reload this page.
Summary
~/.carboncode/config.jsonfor DeepSeek API key and base URL changesWhy
Issue #95 notes that changing provider connection settings currently requires restarting Carbon Code. The TUI constructed one
DeepSeekClientat startup, and both context folding and the subagent closure retained that original client.This change atomically replaces the client after the current turn finishes, so dashboard or config-file edits take effect within about one second without losing conversation state.
Addresses the configuration hot-reload suggestion in #95 without closing the broader issue.
Validation
npm run verify