{"version":"2.1.290","anchor":"remote-control-detail-messages-and-git-index-steering-text-r","canonical_anchor":"remote-control-detail-messages-and-git-index-steering-text-r","heading":"Safer advice when a git index or HEAD file is a link","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-control-detail-messages-and-git-index-steering-text-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Safer advice when a git index or HEAD file is a link\n\nWhen .git\/index or HEAD is a link, the message now says to look at the file and not to run git in that folder\n\n**What**\n\nA link is a file that points to another file somewhere else. When `.git\/index` or `HEAD` is a link, the message Claude Code shows now says to look at the file named index and not to run git in that folder, because git would write through the link to whatever it points at. Before, it said to inspect the link with `ls -l` and remove it before running any git command there.\n\n**Why**\n\nThe advice no longer leads anyone, Claude included, to run commands inside a checkout that may be pointing somewhere unexpected.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}