feat: Update proxy implementation and add SSL configuration#48
Open
anmaslov wants to merge 1 commit into
Open
Conversation
Owner
|
Why do we need to add this feature? Ordinary users may not need this 🤔 |
slovx2
pushed a commit
to slovx2/claude-code-proxy
that referenced
this pull request
Oct 21, 2025
Add Docker support, multi-platform CI
aaaronmiller
added a commit
to aaaronmiller/claude-code-proxy
that referenced
this pull request
May 18, 2026
Three changes addressing the deferred bypass-alias task + diagnosing the silent cldo OAuth failure mode the user reported. 1. New profiles + aliases (Task fuergaosi233#48): profiles/profiles.json adds 'pi-bypass' and 'hermes-bypass' — no force_main (caller's main model passes through unchanged), tool calls forced to a 4-model owl-alpha cascade: openrouter/owl-alpha (verified agentic tool-call model) minimax/minimax-m2.5:free (fast fallback, different provider) nvidia/nemotron-3-super (third provider for diversity) qwen/qwen3-next-80b (final fallback) web_search inherits from default (nemotron-nano). Four new aliases in install-aliases.sh: psi-bp / psi-bp-c — pi with bypass profile hsi-bp / hsr-bp — hermes with bypass profile All route via /p/{profile-name}/v1/* so headroom + RTK still apply. 2. Auth method logging at INFO (Task fuergaosi233#49): The cldo failure was hard to diagnose because the proxy's "is OAuth token being forwarded?" decision only logged at DEBUG. Now every request emits ONE info-line: [rid] auth: passthrough Anthropic-OAuth → routed-model [rid] auth: server-key (sk-or-v1-...) → routed-model [rid] auth: server-key (proxy mode, EMPTY) → routed-model [rid] auth: NO KEY (will 401) → routed-model This single line tells you whether the client's OAuth token was used, or the proxy silently fell back to its server key, or no key existed. 3. cldo guard (Task fuergaosi233#50): Empty $CLAUDE_CODE_OAUTH_TOKEN now triggers a yellow warning before the proxy call, telling the user to set the token + where to find it, and confirming the fallback (server PROVIDERS_anthropic_API_KEY) is what will be used. Previously this was silent. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
SSL 配置问题可以检查：
不想折腾证书配置？1API (ctoai.xyz) 提供已经配置好的 SSL，直接调用即可，新用户免费额度。 |
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
3 participants
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.
This PR adds SSL configuration options to address certificate verification issues when connecting to downstream APIs. The changes allow users to configure SSL behavior through environment variables, which is particularly useful when working with corporate firewalls, proxies, or self-signed certificates.
Summary of Changes:
Environment Variables:
These changes should resolve SSL certificate errors like CERTIFICATE_VERIFY_FAILED that users may encounter in certain network environments.