Conversation
czpython
force-pushed
the
codex/issue-383-provider-env
branch
from
October 3, 2026 15:37
35d246e to
7ee1d92
Compare
Owner
Author
|
Closing without a change. Claude Code chooses |
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
1 participant
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.
A harness launch unsets every provider credential variable except the one that holds the run's own credential. A sandbox can inject a competing value, for example the
ANTHROPIC_API_KEYthat Docker Sandboxes sets, and the CLI can read it instead of the Druks placeholder. The agent's billing mode and its model's provider select the variable to keep.The sandbox applies this once to every harness run. A Chat adapter starts the same way. The bridge keeps the reply command of the turn, so the conversation title runs with the credential of that turn.
Closes #383. Linear: DRU-693.