[BUG] Desktop - Private GitHub repo plugin marketplaces blocked by network egress whitelist requiring `.com` domain format

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Connecting a private GitHub repository as a plugin marketplace is impossible for organizations that manage network egress settings, due to an incompatibility between the two requirements:

1. Private repo marketplaces must be specified in owner/repo format
2. Network egress whitelist only accepts .com domain entries

Since the owner portion of owner/repo is not a .com domain, there is no valid way to whitelist it — causing Claude Desktop to block access to the private marketplace entirely.

What Should Happen?

Organizations should be able to whitelist the GitHub owner/org name (or a pattern like github.com/owner) so that private repo plugin marketplaces configured via owner/repo are accessible.

Error Messages/Logs

Network egress whitelist settings only accept `.com` domain format. The `owner` in `owner/repo` cannot be expressed as a `.com` domain, making it impossible to authorize access to private repo marketplaces.

Steps to Reproduce

1. Configure a private GitHub repository as a plugin marketplace source using the required owner/repo format
2. Attempt to add the repository owner/org to the organization's network egress whitelist in Admin settings
3. Observe that the whitelist only accepts .com domain format entries
4. Result: no valid whitelist entry can be created for the owner portion of owner/repo, and access to the private marketplace is blocked

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.69 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

I am aware this is the claude code repo but I can't figure out where else to file this issue