[Bug] Private marketplace clone fails with HTTPS authentication error

[zekus]

Bug Description private marketplaces are no longer working. /pluging marketplace add https://github.com/<ORG>/<repo> fails with Error: Failed to clone marketplace repository: HTTPS authentication failed. You may need to configure credentials, or use an SSH URL for GitHub repositories.

Environment Info

• Platform: darwin
• Terminal: ghostty
• Version: 2.0.67
• Feedback ID: 67a99628-2df1-473f-9b9b-9d423b760997

Errors

[{"error":"Error: Failed to clone marketplace repository: HTTPS authentication failed. You may need to configure credentials, or use an SSH URL for GitHub repositories.\n\nOriginal error: Cloning into '<redacted>'...\nfatal: could not read Username for 'https://github.com': terminal prompts disabled\n    at K$T (/$bunfs/root/claude:978:151)\n    at async _dR (/$bunfs/root/claude:984:1859)\n    at async aF (/$bunfs/root/claude:986:601)\n    at async <anonymous> (/$bunfs/root/claude:3826:5171)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-12T13:53:45.665Z"},{"error":"Error: Failed to clone marketplace repository: SSH authentication failed. Please ensure your SSH keys are configured for GitHub, or use an HTTPS URL instead.\n\nOriginal error: Cloning into '<redacted>'...\nCould not stat /<redacted>/.ssh: Permission denied\r\nFailed to add the host to the list of known hosts (/<redacted>/.ssh/known_hosts).\r\[email protected]: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n    at K$T (/$bunfs/root/claude:978:151)\n    at async _dR (/$bunfs/root/claude:984:2324)\n    at async aF (/$bunfs/root/claude:986:601)\n    at async <anonymous> (/$bunfs/root/claude:3826:5171)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-12T13:53:46.269Z"},{"error":"Error: Failed to clone marketplace repository: SSH authentication failed. Please ensure your SSH keys are configured for GitHub, or use an HTTPS URL instead.\n\nOriginal error: Cloning into '<redacted>'...\nCould not stat <redacted>/.ssh: Permission denied\r\nFailed to add the host to the list of known hosts (/<redacted>/.ssh/known_hosts).\r\[email protected]: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n    at K$T (/$bunfs/root/claude:978:151)\n    at async _dR (/$bunfs/root/claude:984:2324)\n    at async aF (/$bunfs/root/claude:986:601)\n    at async <anonymous> (/$bunfs/root/claude:3826:5171)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-12T13:53:46.269Z"},{"error":"Error\n    at <anonymous> (/$bunfs/root/claude:46:15227)\n    at <anonymous> (/$bunfs/root/claude:60:10246)\n    at emitError (node:events:43:23)\n    at <anonymous> (/$bunfs/root/claude:59:3466)\n    at emitError (node:events:43:23)\n    at <anonymous> (node:_http_client:248:22)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/claude:62:2147)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-12T13:53:54.291Z"},{"error":"Error: Failed to clone marketplace repository: HTTPS authentication failed. You may need to configure credentials, or use an SSH URL for GitHub repositories.\n\nOriginal error: Cloning into '/<redacted>/.claude/plugins/marketplaces/temp_1765547676330'...\nfatal: could not read Username for 'https://github.com': terminal prompts disabled\n    at K$T (/$bunfs/root/claude:978:151)\n    at async _dR (/$bunfs/root/claude:984:2516)\n    at async aF (/$bunfs/root/claude:986:601)\n    at async <anonymous> (/$bunfs/root/claude:3826:5171)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-12T13:54:36.526Z"}]

[github-actions[bot]]

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/13553
2. https://github.com/anthropics/claude-code/issues/9719
3. https://github.com/anthropics/claude-code/issues/9730

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[knksmith57]

+1, we're now seeing this as well

---

Additional observations from local debugging:

Environment context:

• ssh -T [email protected] succeeds in the same terminal session
• git ls-remote [email protected]:[org]/[repo].git succeeds via Claude Code's Bash tool
• SSH_AUTH_SOCK environment variable is present

Local version history (from debug logs):

Date	Version	Observation
2025-11-18	2.0.43	Private marketplace add succeeded
2025-12-09	2.0.62	Plugin cache refresh from private marketplace succeeded
2025-12-12	2.0.67	SSH fails, HTTPS fallback fails with "terminal prompts disabled"

Workaround:

Add new private marketplace (manual clone, then register)

git clone [email protected]:org/marketplace.git ~/.claude/plugins/marketplaces/<name>

Update existing marketplace

git -C ~/.claude/plugins/marketplaces/<name> pull

Update installed plugin (works after marketplace is updated)

claude plugin update <plugin>@<marketplace>

If plugin update fails with "not found", reinstall to fix corrupted metadata

claude plugin uninstall <plugin>@<marketplace>
claude plugin install <plugin>@<marketplace>

Claude Code separates marketplaces from installed plugins:

~/.claude/plugins/ ├── marketplaces// # git repos containing plugin manifests (registry) ├── cache//// # installed plugin files └── installed_plugins.json # tracks installed versions + metadata

git pull updates the marketplace (the catalog of available plugins and versions), but doesn't touch the installed plugin in the cache. Running claude plugin update afterward:

1. Reads the updated marketplace manifest
2. Compares installed version vs available version
3. Copies new plugin files to cache
4. Updates installed_plugins.json

Analogous to apt update (refresh index) vs apt upgrade (install updates).

[yeroc]

Also bitten by this. Connecting over https protocol with git credential caching enabled and never had an issue until now. Will try downgrading back to 2.0.62 as it seems like .63 must be where the issue was introduced.

I would say this ticket and #13553 are definitely duplicates though.

[kostyay]

Same problem, using git with https protocol. It suddenly stopped working few days ago.

[knksmith57]

Agreed. Chiming back in to confirm that this is definitively still a problem on 2.0.71.

Also that the opacity here sucks. And that immediately breaking what is probably the most valuable and interesting feature for small teams like mine after pushing everyone to adopt it is a real suckerpunch move.