{"version":"2.1.283","anchor":"privatelocal-host-detection-list-greatly-expanded","canonical_anchor":"privatelocal-host-detection-list-greatly-expanded","heading":"More local and private host names are recognised and rejected in git remotes","tier":"notice","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/privatelocal-host-detection-list-greatly-expanded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### More local and private host names are recognised and rejected in git remotes\n\nThe check that spots local or private git remote hosts now covers Docker, minikube, home-router and dev DNS names, and this machine's own hostname\n\n**Unclear.** What uses the result of this check is not confirmed; it may be choosing the source for a cloud session.\n\n**What**\n\nClaude Code checks whether a git remote points at a local or private host, and rejects it if so. A git remote is the address a repository pushes to and pulls from. The check now recognises many more names:\n\n- host names used by Docker, minikube, Rancher, k3d and OrbStack, such as `docker.for.mac.host.internal`\n\n- development wildcard DNS domains such as `.localdev.me`, `.local.gd`, `.ddev.site` and `.lndo.site`\n\n- home network names ending in `.lan`, `.home` and `.fritz.box`\n\n- any host name that matches this machine's own host name\n\n**Why**\n\nIn practice, repositories whose remotes point at a local development host are now rejected by this check.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}