{"version":"2.1.288","anchor":"github-clones-fall-back-to-https-when-ssh-is-not-set-up","canonical_anchor":"github-clones-fall-back-to-https-when-ssh-is-not-set-up","heading":"GitHub clones switch to HTTPS when SSH is clearly not set up","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/github-clones-fall-back-to-https-when-ssh-is-not-set-up","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### GitHub clones switch to HTTPS when SSH is clearly not set up\n\nClaude Code now clones a `git@github.com` address over HTTPS when SSH is clearly not configured, and retries with SSH if HTTPS fails\n\n**Unclear.** It is not confirmed which clone paths actually use the new fallback.\n\n**What**\n\nWhen Claude Code clones a repository from GitHub, it first checks whether SSH (a way of connecting with a key stored on your computer) is set up. That check used to give a plain yes or no. It now answers configured, not configured, or unknown.\n\nA clone of a plain `git@github.com` address now goes over HTTPS instead, showing \"SSH not configured, cloning via HTTPS\", when all of these hold:\n\n- You are not on Windows.\n\n- No `GIT_SSH` override is set.\n\n- SSH is clearly not configured.\n\nIf an HTTPS clone fails, Claude Code shows \"HTTPS clone failed, retrying with SSH\" and tries SSH.\n\n**Why**\n\nThis matters most for plugin and marketplace installs, which clone from GitHub. Users without SSH keys set up should see fewer failed clones.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}