{"version":"2.1.290","anchor":"git-origin-lookup-now-logs-when-the-git-config-cant-be-read","canonical_anchor":"git-origin-lookup-now-logs-when-the-git-config-cant-be-read","heading":"Claude Code logs when it cannot read a repository's git config","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/git-origin-lookup-now-logs-when-the-git-config-cant-be-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Claude Code logs when it cannot read a repository's git config\n\nLooking up a repository's origin now logs when the git config cannot be read instead of silently using the default\n\n**Unclear.** What Claude Code does after the lookup returns the marker is not known.\n\n**What**\n\nWhen Claude Code looks up a repository's origin, the address it was cloned from, it reads the repository's git config. If it cannot read that config, it used to quietly fall back to a default origin. It now logs that it could not read the git config and returns a marker saying so instead.\n\nSeparately, a helper that handles folder names now rejects any name containing a NUL byte, an invisible character that can confuse file handling.\n\n**Why**\n\nThis makes reading git config safer against unusual characters and unsafe paths, and leaves a log line when the read fails.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}