claude-code - 💡(How to fix) Fix [BUG] Marketplace update fires unconditional `ssh -T [email protected]` probe despite CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

Code Example

[pid 107447] execve("/run/current-system/sw/bin/ssh", ["ssh", "-T", "-o", "BatchMode=yes", "-o", "ConnectTimeout=2", "-o", "StrictHostKeyChecking=yes", "[email protected]"], ...) = 0
[pid 107447] connect(4, {sa_family=AF_UNIX, sun_path="/home/$USER/.1password/agent.sock"}, 110) = 0
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

The plugin marketplace update path executes an unconditional ssh -T [email protected] connectivity probe before fetching a marketplace, even when CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1 is set and the marketplace's origin is already an HTTPS URL. The probe doesn't affect functional outcome (the HTTPS fetch succeeds either way), but it noisily wakes the user's SSH agent — for users on 1Password / gnome-keyring this means a popup or authorization prompt every time the marketplace is refreshed.

What Should Happen?

When CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1 is set (or the resolved marketplace remote is already HTTPS), skip the ssh -T [email protected] probe entirely.

Error Messages/Logs

strace -fe trace=execve,connect on the claude process tree captures the probe:

[pid 107447] execve("/run/current-system/sw/bin/ssh", ["ssh", "-T", "-o", "BatchMode=yes", "-o", "ConnectTimeout=2", "-o", "StrictHostKeyChecking=yes", "[email protected]"], ...) = 0
[pid 107447] connect(4, {sa_family=AF_UNIX, sun_path="/home/$USER/.1password/agent.sock"}, 110) = 0

Meanwhile, the actual fetch is pure HTTPS: trace: run_command: GIT_DIR=.git git remote-https origin https://github.com//.git

So the SSH probe is purely informational — it never affects the fetch path.

Steps to Reproduce

  1. Configure a custom marketplace with a github source (HTTPS remote in the resulting marketplace clone).
  2. Set CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1.
  3. Click "Update marketplace" (or trigger marketplace auto-update).
  4. Observe an SSH agent authorization prompt every time, even though no SSH access is used for the actual fetch.

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.137

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING