Repository navigation
fix(claude): align proxy placeholder authentication with upstream - #556
Merged
Merged
Conversation
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.
Claude proxy takeover could write
PROXY_MANAGEDintoANTHROPIC_API_KEYfor providers such as OpenCode Go, triggering Claude Code's custom-key confirmation or conflicting credential warning.Align with upstream #8111: ordinary proxy routes use only
ANTHROPIC_AUTH_TOKENin the client configuration and clear staleANTHROPIC_API_KEYvalues. Provider credentials, upstream authentication, managed-account field selection, and direct mode are unchanged.Fixes #554.
Validation:
cargo fmt --checkpassed;cargo clippy --lib --no-default-featurescompleted with 14 existing warnings outside this change.managed_session_disable_last_app_does_not_terminate_when_status_probe_failsfails on both this branch and unchanged main (4dfe82f4), at the same process-liveness assertion. No daemon behavior changes are included.