{"version":"2.1.296","anchor":"github-ssh-to-https-check-now-works-on-windows","canonical_anchor":"github-ssh-to-https-check-now-works-on-windows","heading":"GitHub SSH check now reads your SSH setup on Windows","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/github-ssh-to-https-check-now-works-on-windows","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### GitHub SSH check now reads your SSH setup on Windows\n\nOn Windows, the check that decides whether to stay on SSH for GitHub now reads your SSH configuration instead of stopping straight away\n\n**Unclear.** Whether this makes Windows connections to GitHub stay on SSH or switch to HTTPS more often is not clear.\n\n**What**\n\nSSH and HTTPS are two ways git can connect to GitHub. Claude Code has a check that decides whether to stay on SSH for GitHub.\n\nOn Windows this check used to give up immediately. It now runs `git ls-remote` with `GIT_SSH_COMMAND` set so that SSH prints its configuration, and reads that configuration to decide.\n\n**Why**\n\nOn Windows, the choice between SSH and HTTPS for GitHub now depends on how your SSH is actually set up, as it already did elsewhere.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}