fix: load macOS system certificates and handle NO_PROXY blackhole for Bun runtime (closes #24470)#76640
Open
botbikamordehai2-sketch wants to merge 1 commit into
Conversation
… Bun runtime (closes anthropics#24470)
This was referenced Jul 11, 2026
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.
What
Claude Cowork fails to connect to the API with 'Self-signed certificate detected' error on macOS when using the Bun runtime introduced in v2.1.17+. The issue occurs because the Bun runtime's SSL context doesn't automatically load macOS system certificate store, and environment variables like NODE_EXTRA_CA_CERTS are not respected by the native binary.
Fix
_check_anthropic_connectivity()to load macOS default certificates usingssl.create_default_context()with explicit certificate loading/etc/ssl/cert.pem) for the Bun runtimeThe fix ensures that when running under Bun on macOS, the SSL context properly loads system certificates so API connections work on clean home networks without requiring manual environment variable configuration.
Closes #24470