You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
GitArea: what it touches
ImprovementsKind: in v2.1.296,
ImprovementsSection of the release
Unclear What Claude Code does when the ANTHROPIC_CUSTOM_HEADERS values match or differ is not known.
What
These changes affect how Claude Code sets up git, the version-control tool, in a repository it prepares for a session.
Setup now adds the origin remote using originURL instead of authURL, so the URL that contains credentials is no longer written into the repository's git config. A new originURL field sits next to authURL.
For a governed git setup with a direct-upstreams list, the warning now says every source keeps its upstream URL as origin and no in-session fetches are routed through the git mount. Before, it said every source was reset to its upstream URL after preparation.
Separately, a new check looks at whether ANTHROPIC_CUSTOM_HEADERS holds a non-empty header and whether it matches a value from another source. What that check controls was not shown.
Why
The credentialed URL is no longer stored in the repository's git config, and an inherited GIT_CONFIG can no longer change how Claude Code's git commands behave. Admins of governed git setups should expect sources to keep their upstream URL as origin rather than being reset after preparation.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat Claude Code does when the `ANTHROPIC_CUSTOM_HEADERS` values match or differ is not known.
Anthropic's release notes agreeFixed $.http.fetch in mods refusing a HEAD request when the response declares a Content-Length over the 4 MiB body limit
